RESEND: Enable GCOV Code Coverage

Mike Hearn mh at
Wed Feb 2 07:56:30 CST 2005

On Tue, 01 Feb 2005 10:39:00 -0600, Robert Shearman wrote:
> I think the issue with this patch is that it isn't it doesn't appear to 
> be useful for a significant number of people and could be maintained as 
> an external patch by the people who do think it's useful. Maybe you 
> could try to persuade us as to why everyone should be using gcov?

I'd really like to see this one go in: I think it would not be hard to set
up automated dumps of the gcov output and convert them to something nice
and easy to read. For people who want to volunteer but aren't sure where
to start, or who aren't quite ready to dive into app compat work extending
the test suite is a great thing to do.

In particular it'll let us easily identify things like error codes that
may be incorrect (ie, were guessed). Given the number of times we've been
nailed by people guessing error codes for obscure situations and not
marking them as guesses, any tool that can show what we're not testing
gets a +1 in my book.

Also the patch looks small, it's mostly documentation, and minimally
invasive. I see no reason to reject it, hopefully Alexandre has just been
bogged down with the WM rewrite and the huge volume of patches going in

thanks -mike

More information about the wine-devel mailing list