Yes I see that. Is there anything special one needs to do to get it to process the shared library in addition to the main program?
-----Original Message----- From: Philippe Waroquiers <[email protected]> Sent: Wednesday, June 17, 2026 4:59 AM To: Mark Roberts <[email protected]>; [email protected] Subject: Re: [Valgrind-users] collecting data from a shared library Memcheck must analyze the whole program as otherwise it will not be able to track the state of the memory (if/and where allocated, freed, initialized, ...). Depending on the tool, you might (somewhat) restrict what it tracks. For example, with callgrind, you can start/stop recording the instructions executed using --toggle-collect=<func> Philippe On Tue, 2026-06-16 at 14:02 -0700, Mark Roberts wrote: > Is there a way to have a Valgrind tool, say memcheck, collect data > from a shared library, but not the program calling the library? > > Thank you, > Mark > > > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
