Re: [PATCH] MI Doco

[Bob Rossi <bob_rossi@cox.net>]

On Fri, Jun 09, 2006 at 10:51:30PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 9 Jun 2006 15:11:34 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
> > 
> > On Fri, Jun 09, 2006 at 10:06:34PM +0300, Eli Zaretskii wrote:
> > > > + @smallexample
> > > > + -> -break-insert main
> > > > + <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
> > > > +     enabled="y",addr="0x08048564",func="main",file="myprog.c",
> > > > +     fullname="/home/nickrob/myprog.c",line="68",times="0"@}
> > > > + <- (gdb)
> > > 
> > > Please use "(@value{GDBP})" instead of a literal "(gdb)".
> > 
> > In this context, that's incorrect.  This is actually a literal
> > "(gdb)\n", rather than the result of "show prompt"; MI uses a hardcoded
> > prompt string.
> 
> Are you saying that all the MI examples that use @value{GDBP} are
> incorrect?
> 
> Also, isn't it a bug in MI that it uses a hardcoded string?

No, it's as designed.
24.1.2 GDB/MI Output Syntax

output ==>
    ( out-of-band-record )* [ result-record ] "(gdb)" nl

It allows front ends to simply recognize that GDB is done. It isn't
the same as gdb's prompt.

Bob Rossi