From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb@sources.redhat.com, drow@mvista.com
Subject: Re: gcc 3.4 regression in gdb.cp/namespace.exp
Date: Tue, 16 Mar 2004 16:37:00 -0000 [thread overview]
Message-ID: <yf265d43fzw.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040316023921.33B114B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 15 Mar 2004 21:39:21 -0500 (EST)")
On Mon, 15 Mar 2004 21:39:21 -0500 (EST), mec.gnu@mindspring.com
(Michael Elizabeth Chastain) said:
> David Carlton writes:
> ptype CClass::NestedClass
> There is no field named NestedClass
> (gdb) FAIL: gdb.cp/namespace.exp: ptype CClass::NestedClass
> This has been working fine for me with gdb HEAD, suite HEAD, gcc HEAD,
> -gdwarf-2 since 2004-01-23. I got some FAILs on 2004-01-18 and
> 2004-01-19.
Hmm. Well, I'm checking out gcc-3_4-branch as we speak, so we'll see
how it goes. (And at some point I'll update my mainline GCC, too.)
As Daniel says, this may be a very recent bug in GDB, so you may not
have seen it. (Or it may be that the GCC I'm using is generating
valid DWARF-2 which happens to be different from the current GCC
snapshot, for that matter.)
>> I really hate the way we test our DWARF 2 reader - there's no way
>> to generate the debug info by hand to give a particular scenario,
>> so instead we have to hope that we can find the magic version of
>> GCC and magic way of writing a test case to trigger the bug in
>> question. Sigh.
> Can we write a gdb.dwarf-2 that looks like gdb.stabs, with assembly
> language input in it?
That's a good idea; I'll think about that.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-03-16 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 2:39 Michael Elizabeth Chastain
2004-03-16 16:00 ` Daniel Jacobowitz
2004-03-16 16:37 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 16:33 Michael Elizabeth Chastain
2004-03-16 0:23 David Carlton
2004-03-16 18:25 ` David Carlton
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=yf265d43fzw.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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