https://bugs.winehq.org/show_bug.cgi?id=54341 Eric Pouech <eric.pouech(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech(a)gmail.com --- Comment #1 from Eric Pouech <eric.pouech(a)gmail.com> --- one of the issue is to understand why the game freezes... I'm not convinced that running a managed code capable debugger will help you. It may give the backtrace of the blocked threads (if it's a deadlock), but it won't tell you why this happended. One way forward: - run the game with WINEDEBUG=+relay and then try to get why the game is stuck from that log. that's tedious. tools/examine-relay can help triaging that log. If you really want to debug it, one item that may work is to use a MS debugger (eg WinDbg) from a full fledged windows setup and to use the remote debugging from windbg (running the remote stub + your game under wine). -- 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.