|
From: Dennis L. <pla...@in...> - 2005-08-10 12:49:27
|
Am Mittwoch, den 10.08.2005, 07:17 -0400 schrieb Neal Becker: > Dennis Lubert wrote: > > > callgrind supports valgrind <= 2.4.0 only > > Am Dienstag, den 09.08.2005, 10:30 -0400 schrieb Neal Becker: > >> I have valgrind-3.0.0, and I need callgrind so I can use kcachegrind. I > >> got callgrind from cvs, but configure fails - it says valgrind-3 not > >> supported. Any hints? > >> > >> > > Thank you. Will kcachegrind be usable with valgrind-3.0.0 then? It seems > to require callgrind. The output that callgrind produces is (simply said) an extended of what cachegrind produces. So kcachegrind will read cachegrind (hence the name) output fine, but will lack some additional information, such as the caller tree (callgrind was calltree previously). I dont know how hard it is to adapt callgrind to 3.x but since it was adopted to the 2.4 in roughly a month, I think it wont take long until it is ported to support 3.x (and from what I could see in the code, it seems to be more straightforward to write tools for 3.x than it was from 2.x, but maybe the look into the code was too short) greets Dennis |