http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #26 from Henri Verbeet hverbeet@gmail.com 2012-02-03 14:45:04 CST --- (In reply to comment #25)
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?
If Wine doesn't automatically print one you can sometimes still manually get one with winedbg, but if DRAW_USE_LLVM=0 helps it probably not worth the effort. My impression is that there's just something broken about the way the SUSE 32-bit Mesa packages link to LLVM. I suppose you could also just try gdb, the crash is probably in Mesa / r600_dri.so, somewhere during draw module initialization. This doesn't have a whole lot to do with Wine though.
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.
c0000005 is a pretty generic access violation, it doesn't tell you much on its own.