Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Fri, 27 Mar 2009 08:07:00 -0000	[thread overview]
Message-ID: <49CC3B5D.3060706@redhat.com> (raw)
In-Reply-To: <20090327022150.GC29050@caradoc.them.org>

Daniel Jacobowitz wrote:

> I remember, about five years ago, doing some serious surgery on the
> way the stabs reader reported constructors and destructors.  If I had
> to guess, I'd say this code was needed before that and/or for GCC 2.x.
> But 2.x is pretty scarce on the ground nowadays anyway.  Either that,
> or something for HP aCC.

Eeew... I didn't even think of other compilers and other debug formats. 
I will do what I can to test on some other platforms, but I hope some 
kind soul(s) out there will help me/us out by checking some environments 
to which I do not have access (anything non-GNU/Linux & cygwin). [Pretty 
please?]

> Anyway, good riddance if your patch works!  What's the new PASS?

It's "PASS: gdb.cp/templates.exp: destructor breakpoint". (Big surprise, 
no? Destructors just seem to work if they are not considered "special." :-)

Now, there might be ways to tickle something that this patch removes, 
but my belief is that we can always dig up the code out of CVS and 
reapply, this time with appropriate comments and test cases to explain 
WHY it is necessary.

Keith

PS. Tom Tromey pointed out to me that if this patch goes in, the 
function "get_destructor_fn_field" will become superfluous. I will, of 
course, submit a revised patch for that when/if the time comes.


  reply	other threads:[~2009-03-27  2:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 22:39 Keith Seitz
2009-03-26 22:07 ` Tom Tromey
2009-03-26 22:39 ` Stan Shebs
2009-03-27  2:35 ` Daniel Jacobowitz
2009-03-27  8:07   ` Keith Seitz [this message]
2009-03-27 15:06     ` Pedro Alves
2009-03-27 15:41       ` Joel Brobecker
2009-03-27 17:19       ` Keith Seitz
2009-03-27 17:49         ` Pedro Alves
2009-03-27 19:05           ` Keith Seitz
2009-03-27 19:22             ` Pedro Alves
2009-03-28  0:56               ` Keith Seitz
2009-03-28  8:56                 ` Keith Seitz
2009-03-30 21:46                   ` Pedro Alves
2009-04-01 23:48                     ` Keith Seitz
2009-04-02  3:17                       ` Daniel Jacobowitz
2009-04-02 16:25                         ` Keith Seitz
2009-04-02 16:32                           ` Daniel Jacobowitz
2009-04-02  8:27                       ` Mark Kettenis
2009-04-07 20:54                       ` Pedro Alves
2009-04-07 21:26                         ` Keith Seitz
2009-04-24  6:06                         ` Tom Tromey
2009-04-24 17:54                           ` Keith Seitz
2009-04-24 22:49                             ` Tom Tromey
2009-06-16 18:41                               ` Keith Seitz
2009-03-28 21:19                 ` 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=49CC3B5D.3060706@redhat.com \
    --to=keiths@redhat.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