Re: [cdt-debug-dev] How to develop a non-gdb debugger for CDT?

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

Of course, A is an option. But if you have a library (or libraries) that
implements the API of your debugger, take a look at the CDI interface. It's
a part of org.eclipse.cdt.debug.core plugin.
Unfortunately, the documentation on CDI is not available.

----- Original Message -----
From: "Haim Cohen" <haim.cohen@xxxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Tuesday, September 30, 2003 9:29 AM
Subject: Re: [cdt-debug-dev] How to develop a non-gdb debugger for CDT?


> It seems you have 2 options :
>
> A : Implement gdb MI interface in your debugger. You should check what
> are the gdb commands sent to gdb by CDT, and what is the output of each
> command. You can learn about it by running gdb from command line.
> The interface to gdb is located in the commands and, run them in gdb and
> look at the output to see if you can supply this information from your
> debugger.
>
> B : Using the existing interface of your debugger, create new commands
> and output classes, to interact with your debugger. There is some
> parsing work here, so plan your debugger interface carefully.
>
> Of course, instead of running the local gdb, run your debugger.
>
> I am curious - what is the DSP you develop the debugger for ?
>
> Haim
>
>
> Felix Yuan wrote:
> > Hi Haim,
> > thank you for your reply.
> >
> > Our projcet is to develop a C compile system for a special DSP. It has a
> > simulator
> > that we can use to debug assemble code.
> > The original plan is to use remote debugging with gdb. But the debugger
team
> > has met some diffculties when they tried to port gdb to our system. So
they
> > select
> > plan B, to develop their own debugger which is not as complex  as gdb
is.
> > They want to wrap the simulator in the debugger and provide some calling
> > interface
> > for debugging. So we must know how CDT is making use of the MI-interface
of
> > gdb as you mentioned. And then we could replace gdb by our own debugger
> > without
> > modifying too many CDT source files.
> > We expect more advice from you.
> > Thanks.
> >
> > Best Regards,
> > Felix
> >
> >
> > ----- Original Message -----
> > From: "Haim Cohen" <haim.cohen@xxxxxxxxxx>
> > To: <cdt-debug-dev@xxxxxxxxxxx>
> > Sent: Tuesday, September 30, 2003 4:50 PM
> > Subject: Re: [cdt-debug-dev] How to develop a non-gdb debugger for CDT?
> >
> >
> >
> >>Hi Felix,
> >>
> >>I have some experience with debuggers in Eclipse.
> >>The interface between the inferior debugger and CDT is the command line
> >>interface of the debugger. CDT is making use of the MI-interface of gdb
> >>- nothing fancy, just output format which is easier to parse.
> >>I suggest you to take a look in CDT code, in the
> >>org.eclipse.cdt.debug.mi.core package.
> >>
> >>I did not find any documentation for this.
> >>
> >>What are your source language and target that you can not use gdb ?
> >>
> >>Haim
> >>
> >>Felix Yuan wrote:
> >>
> >>> Hi,
> >>>Is it possible to integrate a non-gdb debugger with CDT seamlessly?
> >>>If yes, how should we design the debugger? Where can I find the
document
> >>>about the interfaces between CDT UI and debugger engine?
> >>>Thanks in advance.
> >>>
> >>>Regards,
> >>>Felix
> >>
> >>
> >>_______________________________________________
> >>cdt-debug-dev mailing list
> >>cdt-debug-dev@xxxxxxxxxxx
> >>http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> >>
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>