Hi all, I'm evaluating cost of different implementations for a particular algorithm using callgrind.
However, the cost seems to include overhead from valgrind itself, such as malloc & other hooks. (I see in the call graph that malloc calls "malloc_hook_ini" once with a cost of around 60,000 Ir. Having only one a few mallocs in a particluar algorithm this overhead greatly distorts test results. A second problem are symbol resolutions in the C library. Apparently '_dl_runtime_resolve' is called once for each symbol used from the C lib (such as sprintf). This is also unwanted overhead. a) How can I inhibit installation of malloc (and similar hooks)? b) Why are those hooks installed when running callgrind anyway, the prupose of callgrind is not memory error debugging. c) Are there other ways to automatically subtract or exclude this overhead from the test results? (I can use --toggle-collect but I do not want to specify each individual hook, and for _dl_runtime_resolve it does not seem to work properly as on resolve can call another) thanks, Chris ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
