On Mon, 2018-03-19 at 22:31 +0100, Paul Floyd wrote: > Hi > > I’ve been using Massif recently and I gave the xtree output a go (using the > callgrind format output). > > Am I right in saying that, by default, the stats given are for the entire run? Yes.
> This means that the total allocs/frees give a good idea of the memory churn > for the run. Yes. > However, the ‘currently allocated’ will be that on program exit. Yes. > > Is there any easy way to get the ‘currently allocated’ snapshot at the moment > of the peak memory use? Not that I see. > I guess that it’s possible to do one run to find the peak and then another > run and use the gdbserver and the xtmemory command. Yes, that is currently the only way I see. What could be done relatively easily is to add an option to massif to dump the detailed snapshots in callgrind format. Philippe ------------------------------------------------------------------------------ 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
