On Feb 4, 2008, at 12:06 AM, Nicholas Nethercote wrote: > Hi, > > I've written an experimental Valgrind coverage tool, called VCov. > To try it > out, do this: > > svn co svn://svn.valgrind.org/valgrind/branches/VCOV > > Then build in the usual way (see the README file). To run it, use > 'valgrind > --tool=exp-vcov <program>'. > > It's pretty simple. It just records, for each line of source code, > how many > instructions that were derived from that line were executed. It > aggregates > data from multiple executions. It all goes in a file called > "vcov.out". >
Does it do anything callgrind can't do? Several other people (including me) have written similar tools only to realize after the fact that callgrind files are good enough and can even include jumps if you pass --collect-jumps=yes to the args. By letting callgrind collect the data you can spend your time creating the value add of the tool, source integration, report generating etc, without worrying about any of the valgrind stuff. You e-mailed me about the valgrind-tools that I wrote (http:// benjamin-meyer.blogspot.com/2007/12/valgrind-callgrind-tools-part-3- code.html) . Was there any particular reason why it wasn't good enough, I know it isn't perfect, but were you able to get it working at least? -Benjamin Meyer ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
