[Valgrind-users] A great trick for counting cycles using callgrind - but what about massif?

[Peter T. <pt...@li...>]

Hi all

In order to count cycles for part of my C/C++ code I often use

1. #include <valgrind/callgrind.h>

2. add the following macros surrounding the blocks you wish to profile:

CALLGRIND_START_INSTRUMENTATION
..
code I want to profile
..

CALLGRIND_STOP_INSTRUMENTATION

3. valgrind --tool=callgrind --instr-atstart=no command

This is very nice - but a similar procedure/trick apparently does not 
apply for massif.
If I want to monitor memory for a part of the run-time, but not all.
Have I missed something??

It could really be nice to have - so if possible, please add to the list 
of future development ideas.
I might be able to code some of this if I get some help on where to 
start.

Best

-- 
Peter Toft <pt...@li...>