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 <p...@linuxbog.dk> ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
