Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Xavier Roirand <roirand@adacore.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH v2] (Ada) New command to stop at start of exception handlers.
Date: Tue, 19 Dec 2017 16:33:00 -0000	[thread overview]
Message-ID: <834lomptj8.fsf@gnu.org> (raw)
In-Reply-To: <1513693765-20655-1-git-send-email-roirand@adacore.com> (message	from Xavier Roirand on Tue, 19 Dec 2017 15:29:25 +0100)

> From: Xavier Roirand <roirand@adacore.com>
> Cc: Xavier Roirand <roirand@adacore.com>,	brobecker@adacore.com
> Date: Tue, 19 Dec 2017 15:29:25 +0100
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 44f481d..658d93a 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -665,6 +665,9 @@ show max-value-size
>  * Support for reading/writing memory and extracting values on architectures
>    whose memory is addressable in units of any integral multiple of 8 bits.
>  
> +catch handlers
> +  Allows to break when an Ada exception is handled.
> +
>  * New remote packets

This part is OK.

> +@cindex Ada exception handle catching

You mean "handling", I believe, not "handle".  Right?

> +@cindex catch Ada exceptions when handled
> +An Ada exception being handled.  If an exception name is
> +specified at the end of the command (eg @code{catch exception Program_Error}),

"e.g.", and please use @kbd, not @code, when you mean something the
user types as input.

> +When inserting an handle catchpoint on a user-defined
> +exception whose name is identical to one of the exceptions
> +defined by the language, the fully qualified name must be used
> +as the exception name.  Otherwise, @value{GDBN} will assume that it
> +should stop on the pre-defined exception rather than the
> +user-defined one.  For instance, assuming an exception called
> + @code{Constraint_Error} is defined in package @code{Pck}, then the
> +command to use to catch such exceptions handling is
> +@kbd{catch handle Pck.Constraint_Error}.

This is OK Texinfo-wise, but I wonder whether this default is useful.
Why not default to the user-defined exception instead in such cases?
(I'm not an Ada programmer, so apologies if this makes no sense.)

The documentation parts are okay with the above nits fixed.


  reply	other threads:[~2017-12-19 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 14:30 Xavier Roirand
2017-12-19 16:33 ` Eli Zaretskii [this message]
2017-12-20  4:46   ` Joel Brobecker
2017-12-20  4:29 ` 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=834lomptj8.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