|
Hi Joseph.
Truth is, the GDB integration using DSF was originally meant to be such an example.
Although
it has grown much beyond the example stage, I have trouble imagining
a more "solid example", as you put it :)
Also, in your case, since you are not extending GDB, you can look at GDBBackend.GDBProcessStep
which actually lauches GDB; you can launch your debugger instead as a start.
Communication with GDB is done in AbstractMIControl. Each other DSF-GDB service provides
information about an aspect of the debug session by communicating with GDB.
We do not provide new extension points in DSF. However, to launch your own classes, you may
want to either
define a new launch configuration using
extension point="org.eclipse.debug.core.launchConfigurationTypes"
or you can re-use the CDT launch configurations (C/C++ Application, etc) by assigning it a new delegate
using extension point="org.eclipse.debug.core.launchDelegates". You can decide to set your
delegate as the default one (ask this list again when you get there), or your users can choose it
manually like this:
I hope this helps.
Marc
Hi all,
My company has a proprietary C debugger that I am trying to integrate into the eclipse CDT.
The debugger is similar to GDB, but also quite different. It has a command line interface also.
I have search and failed to find any solid examples of how to integrate a custom debugger into eclispse.
Does anyone on this list know of some solid examples of doing this?
Or does anyone know of a good starting place?
I am really at a loss for what extension points I need, or what classes I need to write.
Any help would be awesome.
Thanks,
Joseph Henry.
| 