Apparently I forgot to CC this to the list last time, so here is a new attempt!
Fredrik, if you can modify the source: if any line in a source file
is touched, you'll get a .da file. So you could add a dummy routine
to each file and call them all at startup. That will be an easier
project than
Fredrik Johansson wrote:
> >The untested files are compiled with --fprofile-arcs and
> >-ftest-coverage so they do have .bb and .bbg files (again, I use Gcc
> >3.3.6) so my thinking is to extract the part of gcov.c that count
> >source code lines and create my own tool to do this by reading the
>
Fredrik Johansson wrote:
The untested files are compiled with --fprofile-arcs and
-ftest-coverage so they do have .bb and .bbg files (again, I use Gcc
3.3.6) so my thinking is to extract the part of gcov.c that count
source code lines and create my own tool to do this by reading the
bb-file. But
Hi all!
I'm currently implementing code coverage analysis in an existing
build system. The code tree the system builds consists of "modules"
where some code (and files) is covered by tests and some are not. To
be able to present statistics "per module" I need to know how many
lines of source code
