Re: [Kcachegrind-callgrind] can not get partial dumps of profile data

[Josef W. <Jos...@gm...>]

Hi,

On Thursday 09 March 2006 16:07, Giovanni Sartoni wrote:
>  I am using callgrind 0.9.11  (valgrind-2.2.0) to profile a C++ test
> application that 
> comprises 4 steps, I would like to selectively collect profile data only when
> the application runs the method:
>
> IncrementalTester::step4(void)
> ... 
> callgrind
> -v
> --log-file=reflTestIncrement

This redirects Callgrinds log messages; if you wanted to redirect the profile
data to another file, use "--base=...".

> --num-callers=20

This option has no meaning for Callgrind, that's for memcheck's backtraces
in its error output.

> --simulate-cache=no

Not needed, is default.

> --cacheuse=no

Not needed, is default.
 
> --dump-before=IncrementalTester::step4 
> --dump-after=IncrementalTester::step4

I suppose this is wrong. For C++, callgrind is using demangled C++ symbols,
which include the full signature. So you have to say

 "--dump-before=IncrementalTester::step4(void)"
or
 "--dump-before=IncrementalTester::step4*"


> --collect-atstart=no
> --toggle-collect= IncrementalTester::step4

Should work with "...step4*".

> option --dumpat=<funct> is not valid

That is obsoleted by "--dump-before".


Hope this helps.
Josef