http://bugs.winehq.org/show_bug.cgi?id=11912
--- Comment #3 from quasi-anonymous user from bugmenot.com winehqbugs@bugmenot.com 2008-04-08 11:43:58 --- Created an attachment (id=11979) --> (http://bugs.winehq.org/attachment.cgi?id=11979) git-bisect outputs (see message)
Sorry for answering now, I've been a bit busy before.
Warning : I don't know very well git, so pardon me if I did mistakes. I used the free demo of the game, which is available here : http://www.atomicgamer.com/file.php?id=26176 I did a git-bisect, removing my .wine and doing "make clean" each time, but at a moment (near the end), I couldn't even install the game, so I did a "git-bisect skip" and continued the bisect though I don't know if it was the good thing to do.
Since I was unsure, the attachment contains 3 outputs : the result of "git-bisect log" before doing the "bisect skip" command, then the message git told me about skipping when the bisect was "finished", and finally the "git-bisect log" when it was finished.
The supposed "bad" commit is one of : 125793df0eab65798f53529784e7256d407f2ef0, 1fdae2b2a5b75ca8f7c64bda8f973280107c46ba (see attachment) You can reproduce the bug with the demo (see link above)
Hope it helps. Tell me if I should have done differently.