This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: handle preserving gcov
- From: Ben Elliston <bje at au1 dot ibm dot com>
- To: Robert Henry <rrh at google dot com>
- Cc: gcc at gcc dot gnu dot org, nathan at codesourcery dot com, jh at suse dot cz, dnovillo at google dot com
- Date: Mon, 07 Jul 2008 10:28:33 +1000
- Subject: Re: handle preserving gcov
- References: <c8e291640807030937l44496c05q94fbd2176f9e6fd5@mail.gmail.com>
> Has anybody in the gcov developer community pondered or done such a
> thing?
I have pondered it, yes.
Although it might not be a particularly helpful answer, have you
considered using other tools to get what you want rather than modify
gcov and the runtime code? You could run the instrumented binary with
(say) one set of options, run gcov, gather the coverage output, and then
merge it into an "accumulated" report that includes what you want.
Repeat.
The main downside is that you have to run gcov over ever source file
after each binary invocation and then process the output.
Cheers, Ben
--
Ben Elliston <bje@au.ibm.com>
Australia Development Lab, IBM