Re: gdb/mi

[Andrew Cagney <ac131313@ges.redhat.com>]

> I have some questions/comments about gdb/mi if someone could help out:
> 
> 1. I've configure gdb 5.2 with --enable-gdbmi and --with-uiout. However when I run "gdb --interpreter=mi" the initial messages are not in console stream output format, but later messages are. Is this by design?

You mean the (C) startup message?  No one has thought about that.
(BTW, you no longer need to explicitly configure in GDB/MI, since 5.2, 
it has been enabled by default).

> 2. When I run a target program, it's output is not in target stream output format. Should this be the case?

It depends.

This is a problem that has been discussed before on this list.  If the 
target program is native then GDB would need to do something like play 
with pty's or start a separate terminal program.  If the target is 
remote then the output being encapsulated depends on support for this in 
the remote protocol.

> 3. The gdb/mi output syntax in the manual does not quite reflect reality. In particular the 'console-stream-output', 'target-stream-output' and 'log-stream-output' rules should be suffixed with 'nl'.  Also, I've observed an 'out-of-band-record' appearing after a 'result-record' but the syntax doesn't allow this. I guess it should be something like:
> 
> output -> (out-of-band-record)* [result-record] (out-of-band-record)* "(gdb)" nl

Yes (but I'll fix it a different way).  Good catch.

Andrew