Good morning, We are interested in selectively profiling certain periods of a program's execution. So, we looked in the callgrind manual and it says this:
At the beginning of a program period you want to profile, set the counters to zero (add "CALLGRIND_ZERO_STATS;" into your source), and at the end, dump the profile to a file (add "CALLGRIND_DUMP_STATS;" into your source code). However, we found found that that callgrind 3.6.1 on Centos Linux Version 5.5 x86_32 takes 10 times longer to run even in those parts of the program that are not be selectively profiled by injecting CALLGRIND_ZERO_STATS and CALLGRIND_DUMP_STATS into source code. We were wondering if it possible to make callgrind run more faster when it not selectively profiling a certain period of a program's execution. Thank you. ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
