https://bugs.winehq.org/show_bug.cgi?id=49092 --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- That definitely changes behaviour, but it doesn't fix the problem. Instead I get a series of message boxes complaining of access violations. Also, if I trace back the call to NtSetContextThread() [using __builtin_return_address(0)], I eventually get RtlUnwind() with code STATUS_STACK_OVERFLOW. I think that 36371075f just makes things worse, because while trying to handle a recoverable stack overflow we use another page or two of stack and end up causing an unrecoverable one. I can confirm, though, that allowing the program to actually handle a stack overflow does change its behaviour, and subsequent runs don't run into the same crash... -- 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.