http://bugs.winehq.org/show_bug.cgi?id=12349
--- Comment #14 from Jörg Höhle hoehle@users.sourceforge.net 2008-09-17 05:32:37 --- With 1.1.4, I still obtain reproduceable assertion errors in "der Löwe ist los": After playing "lion catches the parrot's guano on the island", immediately after the application moves on to the next scene.
What stuck me now is that approx. 200 hundred loglines before the assertion failure, wine reports and exception (in the main thread, 0009) and says it's invoking the debugger. No debugger, no backtrace is seen and wine exits little later with the assertion failure (in the dsound thread, often 0018). So the assertion failure may be a side-effect of something else going wrong. For now I don't even know what that thing is, whether it's related to sound or not.
Using 0.9.16, I was unable to crash the game, so the issue can be considered a regression. I tried the same ALSA settings in 1.1.4 as in 0.9.16 (22050Hz, 8 bit). I also tried OSS: same behaviour.
How can I have wine start the debugger immediately in the main thread 0009 (and print a backtrace), instead of dying in 0018?