Re: [Valgrind-users] how to trace an application

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

On Saturday 31 March 2007, Andi Kleen wrote:
> Ashley Pittman <as...@qu...> writes:
> 
> > Josef Weidendorfer wrote:
> > > On Thursday 22 March 2007, Fabian Wein wrote:
> > >> Hello,
> > >>
> > >> is there a way to make a trace of the program run using
> > >> valgrind/callgrind? 
> > > 
> > > You should state what kind of trace you want.
> > > 
> > > E.g. you can get a call tree trace with
> > >  valgrind --tool=callgrind --ct-verbose=1 ...
> > >
> > 
> > That is truly awesome!  It would benefit from strace like command line
> > options and possible a cleaner output format but I can see it being very
> > useful nevertheless.
> 
> Agreed. Strangely the option is not documented either in the usage
> nor in the manpage?

As I said before, this is pure debug output, at verbose level 1.
It was never meant to be for the end user, and as it is now, it really still
is subject to change at minor versions of VG.

If there is interest from users, and we really want to support it as some
kind of first class VG usage, I can try to make a new tool out of it.

BTW, with "--help-debug", you see the option "--ct-verbose" ;-)
But I admit that nowhere it is mentioned what the debug output is at
different verbose levels.

 
> I also noticed it only seems to resolve libc calls to symbols, but not internal
> functions (like main) even though the debuginfo of the program is installed and
> valgrind opened it.

Hmm... that should not happen, as VG's debug info is used as usual.
What VG version, what distribution?

Josef


> 
> -Andi
>