Debugger /windows 10/ dbgeng do not work (and "why python?")

[skavengeer]

Describe the bug
stop work with error
File ".....ghidra_11.3.2_PUBLIC\Ghidra\Debug\Debugger-agent-dbgeng\pypkg\src\ghidradbg\libraries.py", line 20, in
import comtypes
Error: No module named 'comtypes'
No module named 'pybag'
ImportError: cannot import name 'win32' from 'pybag.dbgeng' (....Roaming\Python\Python310\site-packages\pybag\dbgeng_init_.py)

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Config debugging' dbgeng....and all version
2. Click on 'dbgeng'
3. See error
4. No module named 'comtypes' and No module named 'pybag'
5. Lanch dbgeng Failed!

Environment (please complete the following information):

• OS: [e.g. Windows 10]
• Java Version: [e.g. 22.0.1]
• Python 3.10
• Ghidra Version: [e.g. 11.3.2]
• Ghidra Origin: [e.g. official GitHub distro, third party distro, locally built]

[skavengeer]

I am start debugging with old version!!!
Thanks RnmX Inssure " WinDbg (dbgeng) refuses to work entirely #7397 for"Anyway, my current fix is to just install older version"

[d-millar]

Are you up and running now? The current build in master will work with the current version of pybag, but the 11.3.1 distro (I believe) still needs the older version of pybag.

[skavengeer]

Yes, only older version of pybag work....with debugger 11.3.2...I think, that ghidra debugger depend from python is big mistake!
Normaly debugger like Ida pro, x64dbg /x36dbg/ , dnspy ..and filale Ollydbg/only x32/ have not depend anything.

[d-millar]

@skavengeer Glad to hear it's working - keep us posted if you have issues.

Re python, I can certainly sympathize. I am not a dyed-in-the-wool python guy myself, and python versioning is a bit of a nightmare. That said, versioning is a nightmare period, and I'm not sure python is any worse than other languages in this regard.

When you say "depending on python is a big mistake", is your primary objection depending on some external set of libraries or using python at all? In the 25+ years or so that I've been working on debuggers, a python interface has literally been the most requested feature across versions, so, if the latter, you're in the minority there. The alternative for us is relying on JNA or JNI or writing native plugins for windbg. We've done all of these, and I can say without hesitation those are not better solutions. Happy to discuss this in more detail if you're interested, but basically boils down to more versioning problems, additional build constraints, and a generally brittle environment. x32|64|96dbg relies on the TitanEngine, which is built, if I remember correctly, directly on the native debugging interface. Olly, if I remember correctly, accesses the native interface through COM. IDApro, I believe, also wraps the native DLLs. None of these approaches avoids the versioning problem. Ultimately, you are relying on the Nt/Zw Windows system calls or some wrapper around them. These interfaces are sometimes opaque, vary with service pack, and are essentially only one step closer to a direct connection with the debugger. They call it "DLL hell" for a reason, sadly.

In any case, I am going to convert this to a discussion. Feel free to continue the conversation - always interested in others' opinions. And, of course, feel free to open more tickets as issues arise!

[skavengeer]

Thanks for answer, fast and smart! First, I am sorry for may bad english. Maybe I didn't express myself exactly as you understood it.
My experience as software program /from 1977 - Fortran 4, Algol 60, basic, gwbasic, c#, pascal, c, c++, php, java, kotlin,....IDE to C++, Microsoft and Borlan /Embarcadero/ , visual studio,.. System Uinix, Win and Android /sorry for dos 3/..and sorry for my ignorance for python.....Every programming environment is evolving and theoretically it is not possible for a person to know everything, one must allocate resources to familiarize oneself with the specific problem, as I had to read about python now. A program becomes ideal when it is impossible to remove a single line from it in order to make it work. Unfortunately, programs are becoming cluttered with unwanted additions and finding the right path is not so easy. As for the Ghydra disassembler, it is wonderful.
I am sorry for the misunderstanding, but I do not feel like learning more programming languages ​​to complete my task.... I want time to do many more things... to play, draw, fly airplanes and drones... that is why my recommendation was for people unfamiliar with the features of the python language... to read basic things about it first..

[d-millar]

Gotcha and understood! Appreciate the clarification and Feedback!!