From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add support for catch Ada exceptions (take 2)
Date: Wed, 03 Jan 2007 02:47:00 -0000 [thread overview]
Message-ID: <20070103024727.GA30512@nevyn.them.org> (raw)
In-Reply-To: <20070102061526.GH17211@adacore.com>
On Tue, Jan 02, 2007 at 10:15:26AM +0400, Joel Brobecker wrote:
> Apart from that, I'm pretty happy the way the exercise turned out.
Me too. This is OK with just two things: I mentioned xstrprintf to
avoid duplicating strings in another message around when you posted
this, and some calls to error don't use _().
The bits in is_known_support_routine are definitely improvable.
It seems that I should have added some sort of baton to the
breakpoint_ops; that would save you a bunch of stub functions.
If you think that's a good idea, feel free to give it a try :-)
But no need.
> (exception_catchpoint_kind): New enum.
> (function_name_from_pc): New function.
> (is_known_support_routine): New function.
> (ada_find_printable_frame): New function.
You can probably cut this to half the length if you put two functions
on each line:
(exception_catchpoint_kind, function_name_from_pc)
(is_known_support_routine, ada_find_printable_frame): New.
[Except for all of them.]
> NEWS entry and documentation will follow shortly after approval.
Yes please :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-03 2:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 3:20 [RFC/RFA] Add support for catch Ada exceptions Joel Brobecker
2006-12-30 15:55 ` Eli Zaretskii
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 [this message]
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=20070103024727.GA30512@nevyn.them.org \
--to=drow@false.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