From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: make usable with gcc
Date: Fri, 12 Apr 2002 11:51:00 -0000 [thread overview]
Message-ID: <200204121851.g3CIp8i11135@duracef.shout.net> (raw)
mec> . For a nested class definition with v3 dwarf-2 (plus 2.96-rh dwarf-2),
mec> gdb prints two copies of the member function declaration.
mec>
mec> . gdb treats the commands "ptype InnerLocal::NestedInnerLocal" as a
mec> field lookup in the InnerLocal class, failing to find the nested
mec> class named NestedInnerLocal. This happens with both v2 and v3,
mec> both dwarf-2 and stabs+.
mec>
mec> I'm going to put this up for comment for 24 hours and then commit.
mec> After commit, I will file PR's for the bugs.
danj> Thanks! I'll take a look at those to-be PRs when I have a chance.
These are now gnats:gdb/482 and gnats:gdb/483.
My goal is to tag every FAIL in gdb.c++/*.exp with a PR number.
Michael C
next reply other threads:[~2002-04-12 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 11:51 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 20:56 Michael Elizabeth Chastain
2002-04-08 20:15 Michael Elizabeth Chastain
2002-04-08 21:39 ` Daniel Jacobowitz
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=200204121851.g3CIp8i11135@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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