This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA 2/2] Add "undefined-command" error code at end of ^error result...


> Date: Tue, 19 Nov 2013 08:35:26 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > > +  ** The "^error" result record returned when trying to execute an undefined
> > > +     GDB/MI command now provides a variable named "code" whose content is the
> > > +     "undefined-command" error code.
> > 
> > OK, but I would mention the fact that this can be inquired about, as
> > you described in your message.
> 
> OK. New version attached.

Thanks.

> > > +@item "^error" "," "msg=" @var{c-string} [ "," "code=" @var{c-string} ]
> > >  @findex ^error
> > > -The operation failed.  The @code{@var{c-string}} contains the corresponding
> > > +The operation failed.  The @var{msg} variable contains the corresponding
> > >  error message.
> > >  
> > > +If present, the @var{code} variable provides an error code on which
> > 
> > The markup is wrong here: "code" is not a variable, it is a literal
> > symbol.  You probably meant "c-string" instead.
> 
> I've updated both "code" and "msg" (just above). Let me know if it reads
> better for you. ("code" is the name of a variable in GDB/MI lexicon).

It's OK now.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]