| Plugging in a different C debugger? [message #48745] |
Mon, 04 November 2002 14:22  |
Eclipse User |
|
|
|
I need to use a C debugger other than GDB. What would be the appropriate
place to plug this in? I checked the CDT development resources page and list
archives but didn't find anything relevant. In the C/C++ Application Launch
Configuration, Debugger tab, there's a drop down list for the Debugger but
it only has one item in it ("GDB Debugger"). From what I've been able to
tell, CDT talks to GDB through a protocol called MI. So perhaps one way to
go would be to write a class that had MI as its input and output, and
converted it into commands for my other debugger. Is that the preferred way
or would a more native interface that doesn't use MI be better? Any
additional info, examples, pointers, etc. would be appreciated.
Thanks.
|
|
|
| Re: Plugging in a different C debugger? [message #48805 is a reply to message #48745] |
Mon, 04 November 2002 15:34  |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
You should implement the CDI model for your debugger.
It's a part of org.eclipse.cdt.debug.core plugin. The CDI interfaces are
located in org.eclipse.cdt.debug.core.cdi,
org.eclipse.cdt.debug.core.cdi.model and
org.eclipse.cdt.debug.core.cdi.event packages.
Unfortunately, the documentation that describes how these interfaces
communicate is not available now.
The implementation of GDB/MI plugin is based on CDI model, so you can get
some ideas from it.
Mikhail Khodjaiants
"Ed Burnette" <ed.burnette@sas.com> wrote in message
news:aq6fgb$v08$1@rogue.oti.com...
> I need to use a C debugger other than GDB. What would be the appropriate
> place to plug this in? I checked the CDT development resources page and
list
> archives but didn't find anything relevant. In the C/C++ Application
Launch
> Configuration, Debugger tab, there's a drop down list for the Debugger but
> it only has one item in it ("GDB Debugger"). From what I've been able to
> tell, CDT talks to GDB through a protocol called MI. So perhaps one way to
> go would be to write a class that had MI as its input and output, and
> converted it into commands for my other debugger. Is that the preferred
way
> or would a more native interface that doesn't use MI be better? Any
> additional info, examples, pointers, etc. would be appreciated.
>
> Thanks.
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03003 seconds
Home