[Bug 14348] Diablo 2: Unhandled Exception code c0000005

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Feb 3 14:30:11 CST 2012


http://bugs.winehq.org/show_bug.cgi?id=14348

--- Comment #25 from Rafa³ Mi³ecki <zajec5 at gmail.com> 2012-02-03 14:30:11 CST ---
GOOD (Wine 1.3.24):
DRAW_USE_LLVM=0 wine ~/.wine/drive_c/Diablo\ II/Game.exe

So yes, using DRAW_USE_LLVM=0 is another workaround. Unfortunately I can't use
Wine git because of another regression I'm tracking right now. Will post more
details after bisecting.

As for backtrace, I don't get any - at least by looking at stdout and stderr.
Is there any magic wine switch to make it print backtrace?
I think it's not Wine that is crashing, but it's application getting some
not-trackable-for-Wine crash. You can Google for some (rare, but still...)
Windows problem with "Unhandled Exception code c0000005" too.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the wine-bugs mailing list