|
From: Nicholas N. <nj...@cs...> - 2007-08-16 04:04:16
|
On Thu, 16 Aug 2007, Benjamin Meyer wrote: > I saw that this tool was actually listed as one of the suggested tools to > write in the docs > http://valgrind.org/docs/manual/writing-tools.html#writing- > tools.suggestedtools Google didn't return any results so perhaps no one has > written such a tool yet? Any suggestions for a name? How about "secretary"? > Are there any features that you guys would like to see in such a tool? I've worked on one before, as has at least one other person. The problem I had was that it's very difficult to get a coverage percentage. The reason being that you need to know (a) which lines of code are executable, and (b) which lines of code are executed. Valgrind is great for (b), but doesn't help with (a). I tried using debugging info, but found it to be pretty flaky, so much so that I gave up on the tool, because I decided that without per-file coverage percentages it wasn't much use. Nick |