[Bug 57157] New: winedbg: can't attach to windows process

[WineHQ Bugzilla]

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: [e-mail]
          Reporter: [e-mail]
      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.

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #1 from Joe Breuer  ---
Using wine 9.16, I get a number of additional diagnostics concerning debug
symbols, but ultimately the same error / focus does not switch to the
falloutwHR.exe process:

Wine-dbg>info process
 pid      threads  executable (all id:s are in hex)
 00000174 6        'falloutwHR.exe'
 00000088 4        'explorer.exe'
 00000038 9        'services.exe'
 000000ec 6        _ 'rpcss.exe'
 000000cc 3        _ 'svchost.exe'
 000000b4 4        _ 'plugplay.exe'
 00000068 9        _ 'winedevice.exe'
 00000044 8        _ 'winedevice.exe'
 00000020 1        'start.exe'
 00000118 1        _ 'winedbg.exe'
=00000128 1           _ 'winedbg.exe'
> 00000130 9              _ 'Launcher.exe'

00000120 1           _ 'Launcher.exe'
 00000110 2        _ 'conhost.exe'
Wine-dbg>attach 00000174
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"kernelbase"
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"winhttp"
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"advapi32"
[...]
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"netutils"
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"schannel"
012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file
in module L"rsaenh"
syntax error
Wine-dbg>info process
 pid      threads  executable (all id:s are in hex)
 00000174 6        'falloutwHR.exe'
 00000088 4        'explorer.exe'
 00000038 9        'services.exe'
 000000ec 6        _ 'rpcss.exe'
 000000cc 3        _ 'svchost.exe'
 000000b4 4        _ 'plugplay.exe'
 00000068 9        _ 'winedevice.exe'
 00000044 8        _ 'winedevice.exe'
 00000020 1        'start.exe'
 00000118 1        _ 'winedbg.exe'
=00000128 1           _ 'winedbg.exe'
> 00000130 9              _ 'Launcher.exe'

00000120 1           _ 'Launcher.exe'
 00000110 2        _ 'conhost.exe'
Wine-dbg>

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

Eric Pouech  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Eric Pouech  ---
(In reply to Joe Breuer from comment #0)
> 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.

you need 'attach 0x168' instead of 'attach 168'

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #3 from Joe Breuer  ---
exactly the same... "syntax error", focus in 'info process' does not change

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #4 from Eric Pouech  ---
(In reply to Joe Breuer from comment #3)
> exactly the same... "syntax error", focus in 'info process' does not change

you may to detach from current debugged process before attaching to a new one

Wine-dbg> detach
Wine-dbg> attach 0x...
(or start winedbg without arguments)

multiple process support in winedbg still requires some love. you can use two
separate instances of winedbg if you really need to debug the processes in //.

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #5 from Joe Breuer  ---
Aah, thank you! With 'detach' before AND knowing to prefix the PID with 0x, it
works for me.

I strongly suggest to update the docs accordingly, at:

https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Developer%27s-Guide/Debuggi...

Actually - I'll see about updating it with what I had to figure out; since it's
a Wiki on gitlab I should be able to...? If not, I'll add another comment here.

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #6 from Joe Breuer  ---
..., nah, it seems I can't directly edit / suggest changes to wiki pages as a
n00b on gitlab.winehq.org

What's the best process? Fork & PR?

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #7 from Eric Pouech  ---
(In reply to Joe Breuer from comment #6)
> ..., nah, it seems I can't directly edit / suggest changes to wiki pages as
> a n00b on gitlab.winehq.org
>
> What's the best process? Fork & PR?

just added a note to the wiki for not mixing hex & decimal values
will send a patch later on for having a less cryptic message than 'syntax
error'

[Bug 57157] winedbg: can't attach to windows process

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57157

--- Comment #8 from Eric Pouech  ---
(In reply to Eric Pouech from comment #7)
> (In reply to Joe Breuer from comment #6)
> > ..., nah, it seems I can't directly edit / suggest changes to wiki pages as
> > a n00b on gitlab.winehq.org
> >
> > What's the best process? Fork & PR?
>
> just added a note to the wiki for not mixing hex & decimal values
> will send a patch later on for having a less cryptic message than 'syntax
> error'

and commit d1afd8d7f0d8b43c780ea00af1af77051a7edce6 shall implement a nicer
user feed back in that case