From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: keiths@redhat.com
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Thu, 02 Apr 2009 08:27:00 -0000 [thread overview]
Message-ID: <200904020825.n328PWJ2028928@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <49D3FCC9.7090505@redhat.com> (message from Keith Seitz on Wed, 01 Apr 2009 16:46:17 -0700)
> Date: Wed, 01 Apr 2009 16:46:17 -0700
> From: Keith Seitz <keiths@redhat.com>
>
> I have run with gcc 4.2.0, 4.2.4, and gcc 4.3.2 releases (well, F10
> w/4.3.2), and I was finally able to reproduce the failures you mention
> with -gstabs+ (on the 4.2.x compilers). After digging into this for
> quite some time, I am convinced this happens not because of my patch,
> but because stabs is just really broken in gdb.
Well, stabs seems to work reasonable well for plain C on 32-bit
platforms. But I think we basically gave up on stabs for C++ many
years ago already. That's one of the reasons why basically all Open
Source Unix-like OSes switched to DWARF.
next prev parent reply other threads:[~2009-04-02 8:27 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 [this message]
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=200904020825.n328PWJ2028928@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=pedro@codesourcery.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