Detecting gdb state (Was: GDB/MI (Was: Embedded development))
ghost at cs.msu.su
Wed Sep 14 10:07:07 UTC 2005
On Wednesday 14 September 2005 11:51, jbb wrote:
> I'd go with switching to MI and then sending CLI commands if there isn't an
> equivalent MI command. I've never liked the guessing we have to do to see
> if gdb has stopped or not.
BTW, I'm thinking how to solve http://bugs.kde.org/show_bug.cgi?id=110360
where we think that gdb waits for command, while it's busy running program,
and have a simple question. Why don't we use the gdb prompt to detect that?
It might be sligtly less reliable than "^whatever" response in MI, but only
Am I missing something?
> It's very ugly. Being in MI mode should remove
> all that, but being in CLI mode and sending an "experimental" MI command
> would really get you any further forward. However, I'm not the one whos
> doing this :-) so you can ignore my comments :-)
> > This reminds me of:
> > http://bugs.kde.org/show_bug.cgi?id=81277
> > Maybe, we indeed should use GDB window only to show output of user
> > commands, and filter out everything that frontend sends itself?
> That filter idea is good. I think ther are situations where you want to
> show all the interaction with gdb but not all the time. (or instance, when
> I'm curious as to how you actually control gdb).
Yea, we can have a "show all commands" checkbox somewhere.
More information about the KDevelop-devel