public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/9170] Unable to locate constructors with forward-declared classes
Date: Wed, 17 Feb 2010 00:09:00 -0000 [thread overview]
Message-ID: <20100217000950.27885.qmail@sourceware.org> (raw)
In-Reply-To: <20060107214801.9170.thor@math.tu-berlin.de>
------- Additional Comments From pedro at codesourcery dot com 2010-02-17 00:09 -------
Hmmm, the bug the OP has described look very much like PR10966 and PR8166
to me.
Notice the last command on:
http://sourceware.org/ml/gdb/2010-02/msg00090.html
" (gdb) p Foo::Foo
Cannot look up value of a typedef "
His pseudo-patch doesn't have context to know better, so I can't tell
if its essentially the same as the FUNCTIONS_DOMAIN suggestion
on PR10966, or a better fix (it may well be, I may very well misdiagnosed
the real issue, as I didn't bother with it, given that getting rid
of physname gets rid of the bug).
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9170
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-02-17 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060107214801.9170.thor@math.tu-berlin.de>
2010-02-10 22:32 ` tromey at redhat dot com
2010-02-16 23:43 ` thor at math dot tu-berlin dot de
2010-02-17 0:09 ` pedro at codesourcery dot com [this message]
2010-02-17 18:20 ` thor at math dot tu-berlin dot de
2010-02-17 18:25 ` tromey at redhat dot com
2010-03-13 2:47 ` tromey at redhat dot com
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=20100217000950.27885.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).