[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-debug-dev] 2.1.x GDB console feature creep request
|
> Looking at:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=78382
>
> I'm not sure of what you want here. You typed in the GDB console
> monitor
> load
> and the output comes out to the console ... what is the problem ?
Ah, we have a bit of confusion here! :-)
No. The output of "load", "monitor", etc. does not show in the CDT GDB
console.
I copy & pasted the expected output from an Insight session.
We can see in the CDT trace (org.eclipse.cdt.debug.mi.core) that CDT
receives the output from these commands.
> Are you more talking about more UI integration? and in what way?
First CDT should publicly declare that they endorse & support the GDB
console as an execellent compliment to a GUI based debugger frontend.
Stop beating it up.
It may be some time before all issues are worked out, because this is a
difficult, large, but important, feature. Changes to GDB will also be
required before all this is over. CDT & GDB are here for the laung haul.
Some features:
- <tab> (symbol completion)
- "(gdb)" prompt to make it more familiar for GDB experienced engineers
- remove output from CDT's own GDB traffic(Insight has communication
w/the GDB server that there is no evidence of in its GDB console).
- better startup support, e.g.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=79875
> Note:
> - CDT/Debug/GDB uses MI as the protocol of choice,
> the fact that the implementation sometimes(many times)
> falls back to CLI commands is unfortunate and we would like
> to remove it in the future.
>
> - Synchronizing the user console with the
> internal implementation is not easy, for example the introduction
> of "-interpreter-exec" command altough made things a little easier
> to implement the user console did not help in syncing the states.
Difficult is fine.
All the more value of a fully functional CDT.
Thats why top engineers are working on the problem!
:-)
> Maybe the solution is to ... remove the gdb console 8-)
Ne touchez pas mon pot!
GDB Console is every embedded engineers friend and trusty companion.
Lets hear it for the GDB console!
:-)
> and replace it by a "simulacre" that will accept the common gdb commands.
Thats what Insight does, right?
Before anyone asks :-), I'm using CDT more and more for deeply embedded
debugging...
--
Øyvind Harboe
http://www.zylin.com
