http://bugs.winehq.org/show_bug.cgi?id=14662
--- Comment #12 from Corey Hickey bugfood-c@fatooh.org 2011-07-23 14:36:10 CDT --- Ok, I might have what you want. I'm not familiar with debugging wine, so I had to track down the procedure myself and I might have missed some things. Here's what I did:
1. I compiled wine from git last night, which coincidentally was a release version.
commit 8c850a82d440786ca4f83e5e061d6b3d323f5161 Author: Alexandre Julliard julliard@winehq.org Date: Fri Jul 22 19:32:43 2011 +0200
Release 1.3.25.
2. I started wine with: WINEDEBUG=+ddraw,+d3d7 /mnt/64/usr/local/src/wine/wine-git/wine idmain.exe &> /tmp/icewind.log
3. Within wine, I loaded a saved game.
4. On another terminal, I ran the debugger and attached to idmain.exe as described here: http://wiki.winehq.org/Backtraces
5. Back in the game, I moved the party to another area, triggering the crash.
6. In the debugger, I got a backtrace.
I will attach the output of wine and the backtrace.
Thanks again, Corey