public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/14160] function field's "physname" is wrong
Date: Thu, 24 May 2012 15:38:00 -0000 [thread overview]
Message-ID: <bug-14160-4717-Hk0o3HDOn3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14160-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14160
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keiths at redhat dot com
--- Comment #2 from Keith Seitz <keiths at redhat dot com> 2012-05-24 15:38:14 UTC ---
That's only half the story, unfortunately. Yes, half of gdb assumes that this
field (and gsymbols) hold the mangled name. The other half assumes otherwise.
With the dwarf2_physname change, we ended up swapping one for the other.
Clearly it is time to reintroduce the actual linkage name (that would also fix
print demangled bug) and sort out these two halves.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-05-24 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 14:56 [Bug c++/14160] New: " tromey at redhat dot com
2012-05-24 15:06 ` [Bug c++/14160] " qiyao at gcc dot gnu.org
2012-05-24 15:38 ` keiths at redhat dot com [this message]
2012-05-24 16:00 ` tromey at redhat dot com
2012-05-25 20:07 ` tromey at redhat dot com
2012-06-05 20:49 ` tromey at redhat dot com
2012-12-14 20:33 ` cvs-commit at gcc dot gnu.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=bug-14160-4717-Hk0o3HDOn3@http.sourceware.org/bugzilla/ \
--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).