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: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Add support for catch Ada exceptions
Date: Sat, 30 Dec 2006 15:55:00 -0000	[thread overview]
Message-ID: <ubqll2xap.fsf@gnu.org> (raw)
In-Reply-To: <20061230032111.GB27642@adacore.com> (message from Joel Brobecker 	on Sat, 30 Dec 2006 07:21:11 +0400)

> Date: Sat, 30 Dec 2006 07:21:11 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Here is a patch that adds support for "catch"-ing Ada exceptions.

Thanks!

>     (gdb) catch exception
>     Catchpoint 1 on all Ada exceptions at 0x804b7c0
>     (gdb) info break
>     Num Type           Disp Enb Address    What
>     1   catch exception keep y   0x0804b7c0 on all Ada exceptions

I don't like this ``on'' business.  How about removing it?

    (gdb) catch exception
    Catchpoint 1: all Ada exceptions at 0x804b7c0
    (gdb) info break
    Num Type           Disp Enb Address    What
    1   catch exception keep y   0x0804b7c0 all Ada exceptions

>     (gdb) catch exception program_error
>     Catchpoint 1 on `program_error' Ada exception at 0x804b7c0
>     (gdb) catch assert    
>     Catchpoint 2 on failed Ada assertions at 0x804c437
>     (gdb) catch exception unhandled
>     Catchpoint 3 on unhandled Ada exceptions at 0x804ad2d

Again, removing the ``on'' part makes it sound better, IMO:

    (gdb) catch exception program_error
    Catchpoint 1: `program_error' Ada exception at 0x804b7c0
    (gdb) catch assert    
    Catchpoint 2: failed Ada assertions at 0x804c437
    (gdb) catch exception unhandled
    Catchpoint 3: unhandled Ada exceptions at 0x804ad2d

Btw, do we need to display the address?  The fact that you actually
implement this as breakpoints is an implementation detail; the user
doesn't need to know, I think.

> I will also write some documentation, but I want to make sure that
> at least the user-interface is agreed on before I start this work.

You have my blessing for the UI, with the exception of the above minor
comments.  I'm eagerly awaiting to see the docs ;-).


  reply	other threads:[~2006-12-30 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30  3:20 Joel Brobecker
2006-12-30 15:55 ` Eli Zaretskii [this message]
2006-12-31  4:39   ` Joel Brobecker
2006-12-31 21:37 ` Daniel Jacobowitz
2007-01-01  4:42   ` Joel Brobecker
2007-01-01 16:19     ` Daniel Jacobowitz
2007-01-02  6:06       ` [RFA] Add support for catch Ada exceptions (take 2) Joel Brobecker
2007-01-02  6:15         ` Joel Brobecker
2007-01-03  2:47           ` Daniel Jacobowitz
2007-01-04  5:32             ` 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=ubqll2xap.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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