Community
Participate
Working Groups
Provide an integration with the debugging engine that comes with the Debugging Tools for Windows which is part of the Windows SDK. The engine is implemented as a DLL, dbgeng.dll, and provides a C++ interface in dbgeng.h. The intention is to be able to reuse this integration with an integration with the Debug Services Framework (DSF). As such an independent layer that provides the necessary client for the debug engine will be built that will accept commands and generate events.
Windows SDK support has moved out.
This is a enhancement...
BTW, I've restarted this effort. I've decided against using dbgeng.dll. It just isn't documented well enough for me to use, and it isn't redistributable anyway. I've restarted using the pure win32 debug APIs which means I'll be managing breakpoints myself (read/writing memory, should be fun :). Also, I was thinking of doing this with an MI front end and to push off the debug functionality into a separate process, kinda-like gdb. This was necessary due to restrictions I ran into with dbgeng. But since I'm not using that, I'm going to try and do it in Java. I'll bring the win32 and dbghelp APIs to Java using JNI in the same fashion as SWT. Most of the logic will be in Java and easier to debug. I'll also make sure I have a separate CDI layer so that I can create a DSF layer as well. This was my original intention anyway.
Updating the title since I'm not using the Windows Debug Engine (dbgeng).
Returning old defects to pool so I can have an accurate list of what I'm working on.
I think this is still miles away. We need to look at the new EDC debugger which does support windows debugging but with gcc support. We would need to add support for Visual C++ style symbols and stacks to make it complete. The good news is that we're a lot closer than we have been in the past.
It seems Qt Creator integrates with CDB successfully, maybe we should try doing that. Although I don't have anything of value running yet, I have done some initial work, using DSF-GDB as an example of an integration with an external debugger. I plan on working more on that after Juno.
(In reply to comment #7) > It seems Qt Creator integrates with CDB successfully, maybe we should try doing > that. Although I don't have anything of value running yet, I have done some > initial work, using DSF-GDB as an example of an integration with an external > debugger. I plan on working more on that after Juno. Yeah, I was looking at QtCreator a few weeks ago and noticed that. Definitely worth pursuing. Thanks!
LOL, raised this bug over ten years ago. Crossing my mind again now that I'm back on Windows. I am hesitant to build another DSF integration for cdb. We need a solution that work with other IDEs as well. Following the pattern used by lldb by adding an MI layer to it seems reasonable. I'm going to start hacking on this and see what I can come up with. Anyone else interested in helping would be appreciated :).