Nicholas Nethercote schrieb:
> [Forwarding this from the valgrind-developers list in response to a query
> from Robert Lieske about coverage tools]]
>
> ---------- Forwarded message ----------
> Date: Mon, 4 Feb 2008 10:06:34 +1100 (EST)
> From: Nicholas Nethercote <
njn@...>
> To: Valgrind Developers <
valgrind-developers@...>
> Subject: [Valgrind-developers] Experimental Valgrind coverage tool
>
> 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".
[...]
Hi,
that sounds quite like I was looking for. But one thing that I've
wondered about in particular when using Valgrind for coverage is how it
works with C++ templates? If a template is never instantiated, how can a
coverage tool detect that there is source code that is never executed?
Is that possible somehow?
Regards,
Oliver Gerlich
-------------------------------------------------------------------------
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-users mailing list
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
