https://bugs.winehq.org/show_bug.cgi?id=57157 Bug ID: 57157 Summary: winedbg: can't attach to windows process Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jmbreuer.net Distribution: --- I'm trying to debug a hang/freeze concerning Fallout 1 (it's still available on Epic for free for a couple of hours, if someone should want to replicate specifically). Got myself to a point to run winedbg against the game, provoke the hang (in my case, I just need to press Escape to open the in-game save/options/... menu). Now, I want to have a look where all threads of the game are. Wine-dbg>info process pid threads executable (all id:s are in hex) 00000168 6 'falloutwHR.exe' 0000008c 3 'explorer.exe' 00000038 8 'services.exe' 000000e0 6 \_ 'rpcss.exe' 000000c0 3 \_ 'svchost.exe' 000000a8 4 \_ 'plugplay.exe' 00000068 8 \_ 'winedevice.exe' 00000044 8 \_ 'winedevice.exe' 00000020 1 'start.exe' 0000010c 1 \_ 'winedbg.exe' =0000011c 1 \_ 'winedbg.exe'
00000124 9 \_ 'Launcher.exe' 00000114 1 \_ 'Launcher.exe' 00000104 2 \_ 'conhost.exe'
OK, so, switch to falloutwHR.exe first, I guess: Wine-dbg>attach 00000168 syntax error Wine-dbg>attach 168 syntax error Um. What am I doing wrong? Or is there something really weird broken? - I see that there's a testing package of wine 9.16 for my distro (gentoo), I'll try that 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.