Detecting gdb state (Was: GDB/MI (Was: Embedded development))

jbb jbb at
Wed Sep 14 10:34:08 UTC 2005

On Wednesday 14 September 2005 20:04, Vladimir Prus wrote:
> 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
> 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
> slightly less.
> Am I missing something?

Probably not.

We already change the prompt for each command so we can tell what the data is. 
The output in the gdb window is manipulated to show "(gdb) ..." rather that 
the prompt gdb is outputting.

Can't remember quite how it all works, so I'm unsure. It could be a solution.

I'll repeat
> > It's very ugly.

so anything that solves this would be a massive improvement.


More information about the KDevelop-devel mailing list