Re: [Valgrind-developers] Reinstate full functionality of lackey [PATCH]

[Nicholas N. <nj...@cs...>]

On Sun, 30 Oct 2005, Jeroen N. Witmond wrote:

> I don't like to burden Lackey with this, but I'll keep it in mind for the
> next tool I'm working on: Blanket, a basic code coverage tool (mentioned
> in '3.2.2. Suggested tools' in file docs/xml/writing-tools.xml).

Some work has already gone into coverage tools.  Benoit Peccatte was 
working on one earlier this year.  Look for this email to 
valgrind-developers, and others from around the same time.

  Date: Fri, 29 Apr 2005 11:33:38 +0200
  From: Benoit Peccatte <ben...@en...>
  To: val...@li...
  Subject: Re: [Valgrind-developers] Code Coverage

I was also working on a coverage tool (VCov) then.  I've put a tarball of 
my working source directory at www.cs.utexas.edu/~njn/vcov.tar.bz2.  It is 
a bit old -- it uses Vex, but if you SVN update you'll have to make some 
changes to get it to compile again (if you just compile it as is it should 
work).  vcov/vc_main.c is moderately well commented, so hopefully you'll 
be able to understand what's going on.  vcov/vc_annotate.in is the 
annotation script.

The approach taken relies totally on the debug information being present 
and correct -- I don't see how else to do it -- and I found that one 
version of GCC (3.3.4?  can't remember now) was not producing correct 
debug info and so it wasn't working well.

Anyway, IIRC it basically works, although I haven't tested it thoroughly. 
It should serve as a useful starting point, or perhaps you can think of a 
better way of doing things.

Nick