From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: carlton@kealia.com, gdb@sources.redhat.com
Subject: Re: gcc 3.4 regression in gdb.cp/namespace.exp
Date: Tue, 16 Mar 2004 16:00:00 -0000 [thread overview]
Message-ID: <20040316160004.GA7287@nevyn.them.org> (raw)
In-Reply-To: <20040316023921.33B114B104@berman.michael-chastain.com>
On Mon, Mar 15, 2004 at 09:39:21PM -0500, Michael Chastain wrote:
> 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.
Have you run it since I committed the process_structure_scope patch on
Saturday? I won't have time to really parse David's explanation for a
couple of days but it sounds like I broke this.
>
> Do you really need gcc 3.5.0 20040119?
> Can you try gcc 3.5.0 20040315 for example?
>
> > 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?
>
> Michael C
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-16 16:00 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 [this message]
2004-03-16 16:37 ` David Carlton
-- 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=20040316160004.GA7287@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.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