[cdt-debug-dev] Re: cdt-debug-dev digest, Vol 1 #179 - 6 msgs

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

> CDT/Debug is as good as the underlying debugger back-end.
> If the backe-end is gdb and it fails for some reason, it is
> unfair to blame the CDT/Debugger.

One thing I don't like about CDT is that it tries to "hide" GDB and the
GDB console.

Within the embedded crowd, I'm sure there is a huge crowd that has a lot
of Insigh exposure. CDT should tap into these experiences!

E.g. I want to type the GDB commands to connect the debugger to my
target. The menus that "configure" a debug session are just in the way.
At the most I want to be able to specify a GDB command line(including
.gdbinit script).

There is no way to launch the GDB debugger in the "idle mode"(i.e. no
executable/symbol loaded, no target attached) that Insight launches
itself in when insight is launched without any command line parameters.

Øyvind