Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: next/finish/etc -vs- exceptions
Date: Wed, 10 Jun 2009 16:50:00 -0000	[thread overview]
Message-ID: <m3hbyoghit.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090610161204.GB25703@adacore.com> (Joel Brobecker's message of "Wed\, 10 Jun 2009 12\:12\:04 -0400")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> I can't seem to find the time to look at this in more details while
Joel> I'm at the summit, but I always find myself wondering whether it might
Joel> have been possible to use the breakpoint_ops structure rather than
Joel> introducing a couple of breakpoint kinds... I glanced quickly at the
Joel> patch, and I don't think this is the case in this particular instance,
Joel> but did you also look at this option, eventually ruling it out?

Actually I just looked at the longjmp code and did something very
similar.  I will take a look at doing this.

It would be nice if we had a flag day and simply converted everything
to breakpoint_ops.  That's usually the best way to ensure that new
code is written the "right" way (gcc has also had some bad experiences
with these incomplete transitions).

Also, I recently realized that the patch computes the CFA incorrectly.
Really it ought to always compute the Dwarf CFA.  I didn't see a nice
way to do that; if you have any suggestions...

Joel> The feature itself is really interesting, and I wonder if there might
Joel> be something we can do for Ada as well.  As far as I know, there is no
Joel> hook just yet, but maybe we can have it added as well.  After all, I know
Joel> a few people who work on the Ada compiler ;-).

I was under the impression that Ada used longjmp to implement
exceptions, and so the existing longjmp support should work.  (Modulo
the odd bug or two -- I'm not sure if Pedro's fix for the glibc
pointer mangling went in or not.)

Tom


  reply	other threads:[~2009-06-10 16:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 22:32 Tom Tromey
2009-05-30 21:08 ` Doug Evans
2009-05-30 23:18   ` Tom Tromey
2009-06-10 16:13 ` Joel Brobecker
2009-06-10 16:50   ` Tom Tromey [this message]
2009-06-10 17:05     ` Pedro Alves
2009-06-10 17:13       ` Daniel Jacobowitz
2009-06-10 17:47         ` Pedro Alves
2009-06-10 18:32           ` Tom Tromey
2009-06-10 18:49             ` Pedro Alves
2009-06-12 20:49           ` Tom Tromey
2009-06-12 21:51             ` Pedro Alves
2009-06-12 22:07               ` Pedro Alves
2010-11-25  4:54         ` Jan Kratochvil
2009-06-11 14:45     ` Joel Brobecker
2009-06-11 15:47       ` Tom Tromey
2009-07-24 17:38 ` Tom Tromey
2009-07-24 18:54   ` Pedro Alves
2009-07-24 19:18     ` Tom Tromey
2009-09-09 18:56     ` Tom Tromey
2010-10-07  1:37 Tom Tromey
2010-11-24 17:53 ` Joel Brobecker
2010-11-24 18:24   ` Tom Tromey
2010-11-25  7:59 ` Jan Kratochvil
2010-11-27 17:25   ` Doug Evans
2010-11-28  8:29     ` Joel Brobecker
2010-11-30 16:43   ` Tom Tromey
2010-11-30 17:02     ` Jan Kratochvil
2010-11-30 17:15       ` Phil Muldoon
2010-11-30 20:15     ` Tom Tromey
2010-12-01 13:42       ` Jan Kratochvil
2010-12-01 21:40     ` Tom Tromey
2010-11-30 18:23   ` Tom Tromey
2010-11-30 18:55     ` Tom Tromey
2010-12-02 15:32 ` Tom Tromey
2010-12-09 16:37   ` Tom Tromey
2010-12-10  4:52     ` Jan Kratochvil
2010-12-10 20:07       ` Tom Tromey
2010-12-11  5:27         ` Jan Kratochvil
2010-12-15 21:18           ` Tom Tromey

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=m3hbyoghit.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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