Process Hacker and Windows discussion

 
cw2k
Member
Posts: 11

Bug: 'Debug' doesn't work quit well on 64-bit Systems

05 Oct 2016, 03:48

I'm running PH2 64 on some win7 64-bit and a little unhappy how ph2 handles 'attaching' a debugger to some process.

How to do this? Right click on some process and select 'Debug' from the popup-menu.

The thing is that ph2 only uses the 64-bit setting for call the debugger.
Of course if the debugging targets is also a 64-bit process that's perfect,
however if the targets process is 32-bit, running a 64-bit debugger is kinda useless / wrong and will always fail.
A 64-bit debugger can't attach to a 32-bit Process.
(I'm using x64dbgthat has 2 debuggers, one for 32-bit and one for 64-bit. Both attach handler setting are made correctly)

->So can ya make Ph2 64-bit get the 32-bit and 64-bit debugger attach string from the registry and:
if the Process is 32-bit -> Call the 32-bit debugger and
if the Process is 64-bit -> Call the 64-bit debugger.

TIA
 
gust4v

Can't attach a Debugger

13 Feb 2017, 05:33

hello,

whenever i want to attach a debugger, ph2 tells me that it's unable to locate a debugger.
the debug console works and dbghelp.dll has also been found by ph2 itself.

i'm on win7 64bit, using 64bit ph3, 64bit windbg residing in "C:\Program Files\Debugging Tools for Windows (x64)" and tried to attach to an 64bit application.
do i miss any variable, path or registry entry?
 
User avatar
dmex
Admin
Posts: 1328
Location: Australia

Re: Can't attach a Debugger

03 Aug 2017, 07:48

gust4v wrote:
13 Feb 2017, 05:33
i'm on win7 64bit, using 64bit ph3, 64bit windbg residing in "C:\Program Files\Debugging Tools for Windows (x64)" and tried to attach to an 64bit application.
do i miss any variable, path or registry entry?
Windbg is not set as the default system debugger... You need to use both of these registry keys to make windbg the default debugger:
https://github.com/sunnyone/docs/tree/master/aedebug
cw2k wrote:
05 Oct 2016, 03:48
->So can ya make Ph2 64-bit get the 32-bit and 64-bit debugger attach string from the registry and:
if the Process is 32-bit -> Call the 32-bit debugger and
if the Process is 64-bit -> Call the 64-bit debugger.
Sorry for not fixing this issue until now... It's now been fixed in the nightly builds and PH will launch the 32bit debugger for 32bit processes and the 64bit debugger for 64bit processes :thumbup:
https://wj32.org/processhacker/nightly.php

Who is online

Users browsing this forum: Bing and 1 guest