Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: roirand@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA/doco] (Ada) provide the exception message when hitting an exception catchpoint
Date: Fri, 24 Nov 2017 21:44:00 -0000	[thread overview]
Message-ID: <83mv3b8i86.fsf@gnu.org> (raw)
In-Reply-To: <20171124213221.5ltvhfqzapgb2xdz@adacore.com> (message from Joel	Brobecker on Fri, 24 Nov 2017 13:32:21 -0800)

> Date: Fri, 24 Nov 2017 13:32:21 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Xavier Roirand <roirand@adacore.com>, gdb-patches@sourceware.org
> 
> > diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> > index 29d4789..430db0f 100644
> > --- a/gdb/doc/gdb.texinfo
> > +++ b/gdb/doc/gdb.texinfo
> > @@ -27183,7 +27183,9 @@ thread was last seen on.  This field is optional.
> >  Whenever a @code{*stopped} record is emitted because the program
> >  stopped after hitting an exception catchpoint (@pxref{Set Catchpoints}),
> >  @value{GDBN} provides the name of the exception that was raised via
> > -the @code{exception-name} field.
> > +the @code{exception-name} field. Also, for exceptions that were raised

Two spaces, please.

> > +with an exception message, @value{GDBN} provides that message via
> > +the @code{exception-message} field.

Otherwise, the documentation part is OK.

Thanks.


  reply	other threads:[~2017-11-24 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 21:20 Joel Brobecker
2017-11-24 21:32 ` Joel Brobecker
2017-11-24 21:44   ` Eli Zaretskii [this message]
2017-11-24 22:17     ` Joel Brobecker
2017-11-24 23:00 ` Pedro Alves
2017-11-25  2:05   ` Joel Brobecker
2017-11-27 12:11     ` Pedro Alves
2017-11-27 19:42       ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mv3b8i86.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=roirand@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox