Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] GDB, Valgrind and oprofile in non-standard locations (pathnames)

EclipseCon 2004 techical paper page 23 documents an example how you can extend CDT Debugger. It also suggests that you can check and classes as a starting points.


On 15.3.2011 0:53, Petri Tuononen wrote:
As far as I know you might want try to extend the org.eclipse.cdt.debug.core.CDebugger extension point. If you need to set launch parameters specific to your debugger, extend the org.eclipse.cdt.debug.ui.CDebuggerPage extension point.


On 15.3.2011 0:24, Klaus Heinrich Kiwi wrote:
I believe I successfully extended the GNU toolchain plugin to look for
my GCC, AR and AS binaries (using MBS).

But now I need to do the same to GDB, Valgrind and oprofile (those last
two from LTP, I know).

Anyone knows if there are extension points which would allow me to
specify my own debugger (my own gdb version), in the same way MBS allow
us to choose another toolchain?

Any pointers?



Back to the top