http://bugs.winehq.org/show_bug.cgi?id=33193
William Pettersson william.pettersson+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |william.pettersson+wine@gma | |il.com
--- Comment #5 from William Pettersson william.pettersson+wine@gmail.com 2013-03-12 22:18:39 CDT --- (In reply to comment #1)
(In reply to comment #0)
As for the actual crash, it seems its an EXCEPTION_ACCESS_VIOLATION_READ at address 0x128. I would hazard a guess that some Wine function is returning "128" somewhere where SC2 isn't expecting it.
No, that probably means we return NULL somewhere where we shouldn't. A backtrace might be helpful if you have one.
That was me in that thread (enigma), and I'll gladly admit I'm probably wrong, I was just guessing. Unfortunately I'm at work, and won't be home for ~7 or 8 hours, but I'm recompiling wine so I have debugging symbols.
I also have what I thought was a full +relay trace of the crash, but I forgot to check the registry settings and apparently I had "RelayFromExclude"="winex11.drv;user32;gdi32;advapi32;kernel32" set from some early work I'd done on some input issues, so I'll try to recreate that tonight too. However, that's much harder to work with, since triggering the crash involves starting the launcher, starting SC2.exe, logging in, loading a game, selecting some units and killing some bad guys. Last nights relay log file came in at over 8GB.
Unfortunately nothing new to report, but I'll try to get you the requested information.