Is it possible to do below with valgrind (e.g. using client requests)
programmatically
-Iterate over all leaked blocks
-Get the stack trace and leaked memory address
I know above can be done with the combination of gdb and vgdb, I want to know
if this can be done in source code itself.
The program can find, read, and process valgrind's .xml output,
although of course this is another "back door" method.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
