valgrind/kcachegrind integration patch

[Alexander Dymo]

On Saturday 13 January 2007 02:14, Matthew Woehlke wrote:
> Did you mean to write 'valgrind>=2.2'? :-)
> AFAIK --tool=callgrind has been around for a lot longer than 3.x (I have
> 2.2.0, and I use callgrind all the time), so yeah, this should probably
> change. :-)
Hmm. didn't know about that :)

> Um, and I didn't realize kcachgrind understood calltree output (or why
> you would care)... or, at least on my system, "calltree" is a source
> code analyzer and is completely unlike callgrind. Although if you /are/
> talking about that one, it's still valuable because it shows all
> /possible/ paths, not just ones an execution cycle tickles.
kcachegrind here understands both --tool=cachegrind and --tool=callgrind
output. In the later case it shows more information so I used that as a
default.