|
From: Josef W. <Jos...@gm...> - 2003-08-29 13:17:11
|
On Friday 29 August 2003 14:19, Ken Weinert wrote: > Have I just missed this somewhere? Or is it something that valgrind > isn't really suited for? > > I've been looking for something that I could use to easily trace > program flow (trying to sort out a third party library and how it's > being used - I have source, but with callbacks and a data driven > architecture it's not really straightforward) and it just seemed that > valgrind would be able to do this. > > Thanks for any info (oh, btw: the README_DEVELOPERS document seems to > be missing from the valgrind-20030725 distribution.) If it is enough for you to only get the call-graph instead of a full trace (which makes not that much sense because you quickly can get unmanagable huge amounts of trace data), checkout the Calltree skin, together with KCachegrind visualization (kcachegrind.sf.net). The integrated cache simulator can be switched off with "--simulate-cache=no" for faster performance. Josef |