Community
Participate
Working Groups
As an CDT tools developer I would like a debugger framework based on DSF that supports a compete implementation of a C/C++ debugger. This bug is a general description of the Eclipse Debugger for C/C++ (EDC) contribution to CDT, initially created to support the corresponding IPZilla entry.
Source code is now in CVS: See http://nokiacarbideoneclipse.blogspot.com/2009/12/eclipse-debugger-for-cc-edc.html
(In reply to comment #1) > Source code is now in CVS: Yey! Hi Ken, have you tested the EDC debugger with the TCF agent that's in the TM project? If not, do you have an idea of what it would take to get it to work with this agent?
(In reply to comment #2) > (In reply to comment #1) > > Source code is now in CVS: > Yey! > > Hi Ken, have you tested the EDC debugger with the TCF agent that's in the TM > project? If not, do you have an idea of what it would take to get it to work > with this agent? While we've used the TM/TCF agent for reference code I haven't tried using it as an agent in a while. I should try it again to see what works. Off the top of my head I think we would need to: Change EDC to support the standard TCF registers service, not the simplified version we created. We would like to do that anyway. I think EDC is looking for some specific peer attributes, that would need to be sorted out. EDC and it's agents are using two custom services, one for logging console output and the other for pushing host settings down to the agent. These could at least be made optional. Otherwise the interaction between EDC and the agent should be pretty "standard" but I'm sure there would need to be some alignment around various details.
(In reply to comment #3) Thanks Ken.
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.