Hi
Doug,
Toni
has some experience with DSF and CDI working together. (He’s on vacation
for another week.) In our commercial product, he had to do some work to
allow both DSF and CDI to exist together.
The
main problem was breakpoints and which debugger to use for setting them. I
believe if you have one debugger running at a time, you’re ok. However, if
you set breakpoints prior to launching, they default to CDI. We should
definitely discuss this at the CDT summit. I’ll leave the details to Toni
to explain when he gets back.
Doug
P.S.
I like the name. J
Looks like you were the first to get bitten by the new trademark
policy.
From:
dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On
Behalf Of Doug Schaefer
Sent: Thursday, July 26, 2007 10:34
AM
To: Device Debugging developer discussions
Subject:
[dsdp-dd-dev] Windows Debugger
Hey
gang,
If you’ve followed my
work on the CDT, I’m taking a shot at improving it’s usability for desktop
development through my new project called Wascana, http://wascana.sourceforge.net, which
was originally called CDT for Windows. As a key part of that I’ve restarted my
work on the integration with the Windows debug engine. To help me learn DSF, I
would like to use it for the Eclipse side.
But I guess before I
start, I have a question. Does DSF and CDI play nicely together in CDT 4.0.x?
Wascana will come with both Windows SDK support and MinGW gdb which uses CDI, at
least for now. If there are issues and they are simple enough to fix, I’d like
to do so for CDT 4.0.1.
BTW, my integration
uses JSON (www.json.org) to communicate
between Java and a C++ debugger executable that uses IDebugClient and friends.
It’s not MI and I’m free to specify my own protocol giving me flexibility to
decide what goes on the C++ side versus in Eclipse. Should simplify things, in
theory J.
Doug Schaefer,
QNX Software
Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com