Wine FIXME Report January 2010

Michael Stefaniuc mstefani at
Tue Feb 9 14:50:41 CST 2010

On 02/09/2010 08:51 PM, Vincent Povirk wrote:
>> It would be very nice to know if any of the most reported ERRs, WARNs,
>> FIXMEs etc. from the _previous_ run is now gone (in other words, that it has
>> been fixed/implemented)
> I don't think that's possible to determine from the statistics. Just
> because we don't see a message, or don't see it as often, doesn't mean
> it has been solved. Things that have been solved may still appear if
> people are still using older versions.
Actually it is fairly "trivial". Of course not from the statistics but 
from the source code. I have started to work on it some time ago. 
Basically it boils down to:
- Extract the fixme/err format strings from the source code; coccinelle 
makes this task fairly easy (*done*).
- Convert the format string into a regexp.
- Match the regexp against the collected messages. The channel and 
function name already limit the search space a lot.
- Profit.

Having a few Wine versions in the DB will then allow stuff like "first 
seen in/last seen in"; with enough messages in a log file one could even 
fingerprint the Wine version that probably generated that output.
Though this isn't the only reason I started this work but in addition to:
- To better group the messages together based on the source that 
generated those.
- Provide a quick link from the message in the report to the Wine source 
code. To lower the barrier to entry so hopefully people will click on 
that and go "hey, I know how to fix that one".


More information about the wine-devel mailing list