|
From: Taylor H. <wth...@gm...> - 2007-12-20 02:24:43
|
Hi, Can valgrind print the function name of functions when they're invoked? This would be equivalent to putting a printf at the beginning of each function. thanks! - Taylor |
|
From: Julian S. <js...@ac...> - 2007-12-20 02:35:21
|
> Can valgrind print the function name of functions when they're invoked? valgrind --tool=callgrind --ct-verbose=1 <application> J |
|
From: Taylor H. <wth...@gm...> - 2007-12-20 05:26:49
|
Thanks! Can I restrict that output to just functions defined a certain lib? - Taylor On Dec 19, 2007 6:34 PM, Julian Seward <js...@ac...> wrote: > > > Can valgrind print the function name of functions when they're > invoked? > > valgrind --tool=callgrind --ct-verbose=1 <application> > > J > |
|
From: Nicholas N. <nj...@cs...> - 2007-12-20 07:57:02
|
On Wed, 19 Dec 2007, Taylor Holliday wrote: > Thanks! Can I restrict that output to just functions defined a certain lib? Not in Callgrind, AFAIK, but it should easy to do with 'grep' :) Nick |
|
From: Josef W. <Jos...@gm...> - 2007-12-20 13:02:35
|
On Thursday 20 December 2007, Nicholas Nethercote wrote: > On Wed, 19 Dec 2007, Taylor Holliday wrote: > > > Thanks! Can I restrict that output to just functions defined a certain lib? > > Not in Callgrind, AFAIK, but it should easy to do with 'grep' :) As this output is to stderr, you should use something like valgrind --tool=callgrind --ct-verbose=1 <app> 2>&1 | grep ... BTW, the parameters printed are 4-byte values found on the stack, which _could_ be parameters. To be more correct here, one has to parse debug information. Josef |