Re: GDB/MI Output syntax

[Bob Rossi <bob@brasko.net>]

On Tue, Aug 24, 2004 at 03:39:28PM -0400, Bob Rossi wrote:
> On Tue, Aug 24, 2004 at 03:33:30PM -0400, Michael Chastain wrote:
> > Bob Rossi <bob@brasko.net> wrote:
> > > -@code{@var{async-record} | @var{stream-record}}
> > > +@code{( @var{async-record} | @var{stream-record} ) @var{nl}}
> > 
> > I'm dubious about this.
> > 
> > stream-record does not have an NL terminator and needs one, yes.
> > 
> > But async-record already gets an NL terminator in the grammar
> > and does not need a second one.
> > 
> >   async-record -> exec-async-output | status-async-output | notify-async-output
> >   exec-async-output -> [token] "*" async-output
> >   async-output -> async-class ("," result)* nl
> > 
> > For example, gdb.mi/gdb669.exp gives:
> > 
> >   # gdb.log excerpt
> >   ~"[Thread debugging using libthread_db enabled]\n"
> >   ~"[New Thread 8192 (LWP 26606)]\n"
> >   ~"[Switching to Thread 8192 (LWP 26606)]\n"
> >   000*stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",frame={addr="0x0804852d",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff814"}],file="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/pthreads.c",line="81"}
> >   (gdb) 
> 
> Thanks again. I stand corrected.
> We could do, 
>    out-of-band-record ==>
>        async-record | stream-record newline
> 
> does that sound correct?

otherwise if you prefer to have the newline at the bottom of the chain
we could just do 
   console-stream-output ==>
       "~" c-string nl

   target-stream-output ==>
       "@" c-string nl

   log-stream-output ==>
       "&" c-string nl

The first solution is shorter, the second solution is more obvious to
the eye.

Bob Rossi