Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] Another question about Debugger

> Hi all!!! 
>
> I have another question about CDT Debugger. 
>
> How can I log all the dialog between the platform and gdb into Debug Console
> View?

The console view, is reserved for the inferior(the application) output.

> Moreover I want to highligt input and output information by
> different colors.

This sounds like the "Record/Playback" feature,  that was ask in a previous
brainstorming.  It is was push for a future agenda.

> May be someone prompt how to manage information in that View... 
>
> And another one. What are you think about opportunity of posting GDB/MI command from Eclipse? Did CDT Developers  think about it and
> what are their thoughts? 
>

MI, at least in my view, is not meant for users to fiddle with, it is a machine
interface strict/consistent parsing, not something that the user should have
access to.

So it was not in the plan to make GDB/MI "visible".

However, power users will want access to the CLI (gdb prompt) commands.
The initial framework is in, you can switch now to the gdb prompt and enter
commands, (it is an action in the debug view (show debug console) or something).

The problems with the CLI commands are they do not return a kosher MI response.
For example, if you enter:

b file.c:4
^done

CDT/Debug will not be aware of it and the UI will not update and slowly
fall out of sync.  So far, the execution controls like "next, step, etc ..."
are catch before within the MI plugin  but that is awkward.  There will
be some code added later to make the UI aware when you enter a breakpoint
via the command prompt but still ...

Keith @ redhat has done some work to make things easier in gdb-5.4
and also a new interpreter.



Back to the top