On Friday 11 January 2008, Konstantin Serebryany wrote: > Dear valgrind developers, > > How do you usually profile valgrind tools? > > I tried to profile a particularly long run of helgrind with oprofile. > The test runs ~1 second on a real CPU and fails after few hours under > helgrind. > The flat profile (after running for ~20 minutes and then pressing ^C) is: > > 8012128 56.8375 vgHelgrind_nextIterFM > 3130689 22.2089 shadow_mem_make_NoAccess > 1777779 12.6115 is_sane_Lock_BASE > 241600 1.7139 cacheline_wback > 194274 1.3782 avl_find_node > 172924 1.2267 cacheline_fetch > > I wanted to get the callgraph profile with oprofile, but it did not work :( > > Would it be possible to run helgrind under callgrind? Did you try gprof? Any > other suggestions?
Yes. Check out "Self hosting" in README_DEVELOPERS. To run callgrind on a Valgrind tool, you need to specify "--pop-on-jump=yes" for the the outer callgrind. Otherwise, the callgraph will grow linear to run time, producting an "out-of-memory" condition after some time. Note that self hosting is _really_ slow, and it could take a while until you reach the problematic phase. However, you can check out intermediate dumps triggered by "callgrind_control". Josef ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
