| Co-debugging with CDT? [message #85575] |
Thu, 13 November 2003 18:15  |
Eclipse User |
|
|
|
Hello,
I am trying to leverage the CDT to implement a form of "co-debugging" and
would welcome any suggestions.
The "application" is a logical aggregation of proprietary object code
(generated from proprietary assembly language and assemblers/linkers/etc)
and Windows DLLs (written in C++ and compiled using gcc).
To debug this application, we have developed our own debug plugin which
knows how to launch and debug the "application"
To make a long story short, the proprietary object code is run using a
proprietary simulator (an exe running in a standalone process), which is
controlled via our debug plugin. The simulator will load the Windows DLLs
as the application starts up.
Our plugin knows how to set breakpoints, step, etc through the proprietary
object code, but we want to have CDT manage the breakpoints, stepping,
etc. of the Windows DLLs.
Any ideas on how to do this? I have tried using the Attach To Process
functionality of the CDT to attach to the simulator .exe with very limited
success (I can hit a breakpoint, then gdb/CDT seems to get very confused).
Can an attach debug session be accomplished programmitically? How might I
co-mingle the services of our debug plugin with those of CDT?
This is a pretty lengthy and involved question, and appreciate any help I
can get.
|
|
|
| Re: Co-debugging with CDT? [message #85698 is a reply to message #85575] |
Fri, 14 November 2003 08:24  |
| Eclipse User |
|
|
|
Originally posted by: mikhailkhod.rogers.com
The CDT debugger contains a special layer (CDI). The purpose of this layer
is to provide an abstraction of the common debugging operations and make it
independent from the underlying debug engine. CDT also provides an
implementation of the CDI based on gdb/mi protocol.
To solve your problem you can try to implement gdb/mi protocol and hack into
CDT implementation or implement the CDI interfaces.
"Cameron Stevens" <cameron.stevens@qstech.com> wrote in message
news:bp13aq$apc$1@eclipse.org...
> Hello,
>
> I am trying to leverage the CDT to implement a form of "co-debugging" and
> would welcome any suggestions.
>
> The "application" is a logical aggregation of proprietary object code
> (generated from proprietary assembly language and assemblers/linkers/etc)
> and Windows DLLs (written in C++ and compiled using gcc).
>
> To debug this application, we have developed our own debug plugin which
> knows how to launch and debug the "application"
>
> To make a long story short, the proprietary object code is run using a
> proprietary simulator (an exe running in a standalone process), which is
> controlled via our debug plugin. The simulator will load the Windows DLLs
> as the application starts up.
>
> Our plugin knows how to set breakpoints, step, etc through the proprietary
> object code, but we want to have CDT manage the breakpoints, stepping,
> etc. of the Windows DLLs.
>
> Any ideas on how to do this? I have tried using the Attach To Process
> functionality of the CDT to attach to the simulator .exe with very limited
> success (I can hit a breakpoint, then gdb/CDT seems to get very confused).
>
> Can an attach debug session be accomplished programmitically? How might I
> co-mingle the services of our debug plugin with those of CDT?
>
> This is a pretty lengthy and involved question, and appreciate any help I
> can get.
>
|
|
|
Powered by
FUDForum. Page generated in 0.06708 seconds
Home