http://bugs.winehq.org/show_bug.cgi?id=11188
--- Comment #87 from joaopa jeremielapuree@yahoo.fr 2009-01-08 06:20:32 --- The first thing to do is a real regression test to find the real bad commit: http://wiki.winehq.org/RegressionTesting
If the bad commit is 6310819afb0ac294573551c2117f636ed8367ccc actually, then you need to write tests to see what is wrong in this patch.
Reporting again and again that it is broken does not help.