public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/8616] lookup_transparent_type sometimes fails in presence of classes in namespaces
Date: Fri, 19 Feb 2010 21:53:00 -0000 [thread overview]
Message-ID: <20100219215344.27930.qmail@sourceware.org> (raw)
In-Reply-To: <20040114180800.8616.carlton@bactrian.org>
------- Additional Comments From tromey at redhat dot com 2010-02-19 21:53 -------
It seems to me that this can only happen if the compiler is
generating bad debuginfo. And, since the OP couldn't think of
what to do about this, there's no reason to have the bug open.
Recent versions of gcc seem much better in this area, as well.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
http://sourceware.org/bugzilla/show_bug.cgi?id=8616
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
parent reply other threads:[~2010-02-19 21:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040114180800.8616.carlton@bactrian.org>]
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=20100219215344.27930.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).