http://bugs.winehq.org/show_bug.cgi?id=15162 --- Comment #7 from Sam skipsey <aoanla(a)yahoo.com> 2008-09-07 12:51:29 --- (In reply to comment #6)
This patch is not related to your problem. Please do a other one. To be sure that you found the good first bad commit, do the regression 3 times. If you do not find the same commit, your regression is not good.
Joaopa
I did think it looked a little unrelated. The difficulty is that sometimes the crash happens just on resolution change - in which case, the badness of that branch is obvious. In others, it can take a long time for the crash to happen... (so, I suspect that it's my good, rather than bad regressions which are wrong). I'll have another look at it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.