https://bugs.winehq.org/show_bug.cgi?id=37218 --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Created attachment 50511 --> https://bugs.winehq.org/attachment.cgi?id=50511 WINEDEBUG=+dbghelp_msc,+dbghelp winedbg ./Unity.exe Hello folks, attached is a log with of winedbg output with Unity being run loaded (uncompressed size: 19MB). Unfortunately I couldn't use 'dbghelp_symt' channel as it causes an early abort due to debugstr buffer overflow (C++/std namespace with overly long debug symbols) --- snip --- $ WINEDEBUG=+dbghelp_msc,+dbghelp winedbg ./Unity.exe 2> winedbg_output.txt WineDbg starting on pid 0024 DbgBreakPoint () at /home/focht/projects/wine/wine.repo/src/include/winternl.h:2017 0x7b8624bc DbgBreakPoint+0x4 [/home/focht/projects/wine/wine.repo/src/include/winternl.h:2017] in kernel32: popl %ebp 2017 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg>c Thread ID=0031 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0032 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0033 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0037 renamed using MS VC6 extension (name=="UnitySubs") Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x006dd941). Exception 80000101 --- snip --- Regars -- 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.