On Sat, Sep 18, 2010 at 12:58 AM, Josef Weidendorfer <josef.weidendor...@gmx.de> wrote: > On Friday 17 September 2010, Mike Coleman wrote: >> I've tried several times over the years to use the callgrind options >> --dump-before, --dump-after, --zero-before, etc., with a C++ program, >> and I've never been able to get these dumps to happen. >> >> Are these implemented? I've tried using the function names as they >> appear in kcachegrind and I've tried using the mangled names as they >> appear in 'nm -a' output, both with and without the leading >> underscore, but it never seems to work. > > Hmm. They should work... > > With C++, the full signature is part of the function name. > It is easier to use wildcards, e.g. "--dump-after=foo*" to trigger > a dump whenever a function starting with "foo" is left.
Hadn't seen the wildcard thing documented anywhere. That should make life simpler, though I still couldn't get it to fire. If I just say "--dump-after=*f*" (quoted from the shell, of course), would you expect that to fire? I'm a little unclear on whether this works with (say) template class functions in namespaces, etc. Has anyone ever actually seen this work? Googling doesn't turn up much. Mike ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
