http://bugs.winehq.org/show_bug.cgi?id=3058
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2005-15-06 00:35 ------- your relay+all log looks interesting.
I wasn't sure how to get the necessary backtrace using winedbg - WolfSP didn't seem to want to run under the debugger.
hmmm. I am not sure the backtraces will help us, but have you tried this:
$ winedbg /.../WolfSP.exe Wine-dbg>info thread Wine-dbg>cont Wine-dbg>info thread (execute this when the game gets crashed) Wine-dbg>bt all (BackTrace All threads, it sometimes doesn't work for me)
by observing "ntdll.gcc32.partial.log" and "trace.all.gcc32.partial.log" I conclude, that every time game crashes you get very different traces.
if your CW is still on a disk, I recommend checking this by doing several times one of the following: * logging the output of "Wine-dbg>bt all" * logging the tail of "+ntdll" output * logging the tail of "trace+all" output
BTW, in opposition to what Dustin says, I think the formula -900/+10 is more effective, as we aren't interested in the traces of "winedbg" process itself, IMHO. :-P