http://bugs.winehq.org/show_bug.cgi?id=3019
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2005-01-06 13:34 ------- I may not understand something, but you may like doing a regression testing. The page [1] describes this process, during which you can find offending patch.
Probably you will have to check some cvs mailing list archives from [2] to [3] to get exact dates of patches submitted (as your iteration number grows and you get closer to the offending patch).
I suggest to think of it as of bisection alorithm for root-finding (from a numerical analysis). :-)
[1] http://www.winehq.org/site/docs/wine-devel/x1316 [2] http://www.winehq.org/hypermail/wine-cvs/2002/08/index.html [3] http://www.winehq.org/hypermail/wine-cvs/2005/03/index.html
-
Wine Bugs