In the Valgrind User Manual, the Massif chapter mentions: "certain space leaks ... aren't detected by traditional leak-checkers, such as Memcheck's. That's because the memory isn't ever actually lost -- a pointer remains to it -- but it's not in use. ... Massif can help identify these leaks."
The sample program and output graph sections explain how to visually interpret the output after it's run through ms_print, as well as the concepts of detailed and heap snapshots, but there isn't any example given of finding space leaks. What are the high-level steps for doing so? Would users examine the detailed snapshots and analyze the breakdown of memory consumption in specific functions to find references that haven't been used in a while? Thanks, Nicholas, QNX Software Systems Ltd.
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
