https://bugs.winehq.org/show_bug.cgi?id=43652 --- Comment #4 from Adam Szmigin <smidge(a)xsco.net> --- I'm trying to debug this issue using winedbg, but having issues even attaching. $ winedbg EnginePrime.exe (this runs the app as usual, but does not ever give me the debug prompt to add breakpoints or step over, etc.) Pressing Ctrl+C prints a message but never gives me the debug prompt either. The application itself is still usable: ^CCtrl-C: stopping debuggee If I try to run the app and then attach, the debugger hangs: (in one terminal) $ wine EnginePrime.exe (other terminal) $ winedbg Wine-dbg>info process pid threads executable (all id:s are in hex) 00000030 58 'EnginePrime.exe' 0000004f 2 \_ 'OfflineAnalyzer.exe' 0000004d 2 \_ 'OfflineAnalyzer.exe' 0000004b 2 \_ 'OfflineAnalyzer.exe' 00000049 2 \_ 'OfflineAnalyzer.exe' 00000047 2 \_ 'OfflineAnalyzer.exe' 00000045 2 \_ 'OfflineAnalyzer.exe' 00000043 2 \_ 'OfflineAnalyzer.exe' Wine-dbg>attach 0x30 (winedbg just hangs here) The above commands seem to be as recommended in the Wine Developer's guide. Any advice? -- 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.