http://bugs.winehq.org/show_bug.cgi?id=60004 --- Comment #15 from Eric Pouech <eric.pouech@gmail.com> --- (In reply to Tobias (:Tobbi) Markus from comment #14)
The internal SuperTux debugger reports a crash in __CxxUnregisterExceptionObject . No other stack trace, just that one frame. I don't know if this is even relevant at this point.
winedbg prints as back trace: Unhandled exception: page fault on read access to 0x0000000000000008 in 64-bit code (0x006fffff045a63). =>0 0x006fffff045a63 _FindAndUnlinkFrame+0x53(fi=000000000010C5B0) in ucrtbase (0x0000000010c5f0) 1 0x006fffff045a63 __CxxUnregisterExceptionObject+0xa3(frame_info=<internal error>, in_use=<is not available>) in ucrtbase (0x0000000010c5f0) 2 0x006ffffe5529e2 cxx_catch_cleanup+0x12(normal=<has been optimized away by compiler>, c=<is not available> and I find only one (still strange) occurence of 'Unhandled attr op: 2' so basically, it could well be there are three different issues to consider: - the crash in dbghelp when reading dinput8.dll seems to be gone (I'll upstream the relevant patches) (note: that dbghelp is loaded both by supertux2 when setting up its crashhandler and capture backtrace, and winedbg when debugging supertux2) - there's an exception generated (running without winedbg, with WINEDEBUG=+seh,+unwind could help to get some idea where it comes from) - then exception is caught by supertux2 exception handler, and its processing causes another crash (likely in ucrtbase) (it has yet to be defined where the issue comes from) potentially it may be needed to open different tickets for the last two points (as they likely impact different components); but let start by looking at WINEDEBUG=+seh,+unwind output TIA -- 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.