Eclipse Community Forums: C / C++ IDE (CDT) » jumping into the CDT code

Home » Language IDEs » C / C++ IDE (CDT) » jumping into the CDT code

jumping into the CDT code [message #172584]

Tue, 11 July 2006 12:01

Eclipse User

Originally posted by: vaibhavchopda.yahoo.com

Hi all
I am assigned a task of writing a low level debugger GUI for a powerpc
architechture in eclipse. I was wondering if I could reuse any of the
existing CDT code like register views, memory views, etc etc. I am looking
at the CDT code but I am overwhelmed coz its vast and I really dont figure
out where do I start from.

Please can you give me so inputs regarding -
1. What is what in the CDE code ? i.e. Where do I find code for the views,
how are the content providers connected to the GDB etc etc.
2. Any pointers on understanding the CDT code for dummies.
3. Any suggestions on how do I go abt this ?

Thanks a lot for you help.
With Regards
Vaibhav

Re: jumping into the CDT code [message #172934 is a reply to message #172584]

Fri, 14 July 2006 08:39

Eclipse User

vaibhav,

you'll probably have to contribute a new debugger, extending point
org.eclipse.cdt.debug.core.CDebugger. Your new debugger would have to
implement class ICDIDebugger. See the class GDBCDIDebugger for a reference
implementation.

Depending on what needs to be done to launch your debug session you may also
have to contribute a new launch via point
org.eclipse.debug.core.launchConfigurationTypes. There is online
documentation on this, see Platform Plug-in Developer Guide --> Programmer's
Guide --> Program debug and launch support --> Launching a program -->
Adding launchers to the platform.

If your debugger is not gdb-like then you have a respectable amount of work
before you, but on the other hand implementing the launch and the debugger
classes gives you all the debug views for free ...

Good luck!

Norbert Ploett

Re: jumping into the CDT code [message #173585 is a reply to message #172934]

Mon, 24 July 2006 13:25

Eclipse User

Originally posted by: vaibhavchopda.yahoo.com

Thx Nobert and hello to all,
Thanks for your answer, it was a great kick start.
I realize that I 'll be writing a different debugger in the sense it does
not use GDB protocol. Thats why I figure out that I 'll need to change the
model but the front end and the content providers that feed the front end
be same.
What do I exactly change to change the model ? I think the
org.eclipse.cdt.debug.core has a package which has classes which implement
the model components like CRegister.java. I want to know who creates the
machine state by instantiating these classes.

Thanks a lot for help
Regards
Vaibhav

Previous Topic:	Debugging hybrid java C apps
Next Topic:	Frequent GUI updates inefficient ?

Goto Forum:

-=] Back to Top [=-

Current Time: Thu May 08 18:03:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter