http://bugs.winehq.org/show_bug.cgi?id=60281 --- Comment #1 from Nilesh <nileshkumbhar1604@gmail.com> --- I dug into RtlUnwindEx() in dlls/ntdll/signal_x86_64.c a bit and think I might have found something. The stack overflow message ("virtual_setup_exception stack overflow...") shows up right before RtlUnwindEx gets called. So by the time unwinding starts, the stack is basically already full. Inside the function there's a loop that calls call_unwind_handler() on each frame - and my guess is that this call itself needs some stack space, which it doesn't have, so it throws another stack overflow exception mid-unwind. That would explain why target_ip never changes in the trace - it's not really looping normally, it's re-entering the same unwind attempt over and over because each attempt fails the same way. If that's right, this isn't a plain infinite loop bug, it's more like the guard page / stack overflow recovery path not leaving enough headroom for the unwind handler to actually run. Not sure if this is specific to how WoW64 sets up the stack on macOS/Rosetta or if it's more general. Would appreciate it if someone who knows this code better could confirm if I'm on the right track, or point me toward what to check next. -- 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.