|
From: <mma...@ny...> - 2004-07-29 23:48:52
|
Hi, I am looking for an alternative to gcov, which won't need to recompile the entire project. Does anyone know if I can use valgrind for this ? If so can you point me to some documentation on how to do this ? And if possible (you never know!) if this is easy to convert to gcov-like output ? --- I was also looking at Jeremy's patches. Are they still maintained ? Will they be added in valgrind ? In particular I am thinking of vgprof patch. Thanks Mathieu |
|
From: Eric E. <eri...@fr...> - 2004-07-30 01:23:32
|
On Thu, 29 Jul 2004 19:47:49 -0400, <mma...@ny...> wrote: > Hi, > > I am looking for an alternative to gcov, which won't need to recompil= e=20 > the entire project. Does anyone know if I can use valgrind for this ? I= f=20 > so can you point me to some documentation on how to do this ? And if=20 > possible (you never know!) if this is easy to convert to gcov-like=20 > output ? It is in my todo list to launch a debate on a small skin which would do coverage... But doing so is far too easy, so the next item says: "Debate on concurrent skins, so that for example you could ensure that all the code you have covered does no error, e.g. if you are able to run with memcheck + the coverage skin..." > I was also looking at Jeremy's patches. Are they still maintained ?=20 > Will they be added in valgrind ? In particular I am thinking of vgprof=20 > patch. For profiling, have a look at kcachegrind. All that, including Jeremy's patches (but I don't know if they are still up-to-date) is referenced here: http://valgrind.kde.org/related.html Cheers -- Eric |