http://bugs.winehq.org/show_bug.cgi?id=29092
--- Comment #2 from Michael Zapf michael@mizapf.de 2011-11-15 07:03:38 CST --- I tried the instruction on that page, but I was not successful with creating a backtrace:
- I start the application with "wine mystmaster2k-d.exe" - Before the app crashes I start winedbg - Attaching to pid of app + "cont" - Click on link book (usually causes the crash without winedbg) - Application just hangs, no error window popping up, winedbg also hangs after "cont", no output; cannot attach a second time (error 5)
2nd try: - Starting the application, clicking on the book to make it crash - Error window pops up - I start winedbg, try to attach to crashed process, but get error 5
3rd try: - Starting the application in winedbg ("wine winedbg mystmaster2k-d.exe"), cont - Click on link book, after linking sound, program hangs, no reaction in terminal - Can't attach a second time (error 5) - Twice CTRL-C brings up the error window. In the terminal some lines are added
"Ctrl-C: stopping debuggee 0x00321e19: lock jmp *0x0(%ecx) Wine-dbg>Ctrl-C: stopping debuggee wine: Unhandled illegal instruction at address 0x321e19 (thread 003e), starting debugger..."
No more output, I need to close the wine desktop window. Another window then says that the application does not react.
Michael