Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Tue, 07 Apr 2009 20:54:00 -0000	[thread overview]
Message-ID: <200904072154.45602.pedro@codesourcery.com> (raw)
In-Reply-To: <49D3FCC9.7090505@redhat.com>

On Thursday 02 April 2009 00:46:17, Keith Seitz wrote:
> Can you apply the attached patch to your tree and try again?

Since this stabs patch in now in HEAD, I've redone the testing.  I
confirm that with this patch installed, your original patch doesn't
introduce any new failures on the templates.exp test on
stabs --- gcc 4.2, or head.  Yay!

> So, I guess my position is that since stabs is so darn broken any way, 
> we might as well apply the patch and deal with the fallout. At least 
> then we'll know (and hopefully document) WHY all this special casing of 
> dtors is necessary.

On my end, your original patch is clear to go in.

> PS. I still don't understand how you are getting DWARF2 failures. I've 
> run these tests on gcc 4.2.0, 4.2.4, 4.3.2, and 4.4.0, and NONE of those 
> compilers demonstrate any failures after the patch; they all fail BEFORE 
> the patch is applied. I guess I'll deal with this next.

This must be a miscomunication.  I never said I was getting DWARF
failures.  I just re-confirmed that your original patch does remove
the dtors kfail in templates.exp on dwarf.

 -KFAIL: gdb.cp/templates.exp: destructor breakpoint (PRMS: gdb/1112)
 +PASS: gdb.cp/templates.exp: destructor breakpoint

-- 
Pedro Alves


  parent reply	other threads:[~2009-04-07 20:54 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
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 [this message]
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=200904072154.45602.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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