public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/51668] New: class DW_AT_name does not match method's linkage name prefix (char)1 vs. '\001'
Date: Fri, 23 Dec 2011 18:05:00 -0000 [thread overview]
Message-ID: <bug-51668-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51668
Bug #: 51668
Summary: class DW_AT_name does not match method's linkage name
prefix (char)1 vs. '\001'
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jan.kratochvil@redhat.com
CC: dodji@gcc.gnu.org
Target: x86_64-unknown-linux-gnu
PASS: gcc (GCC) 4.6.3 20111222 (prerelease)
FAIL: gcc (GCC) 4.7.0 20111222 (experimental)
>From the GDB point of view it is a regression because gcc-4.7 now provides the
non-matching DW_AT_linkage_name for ctors/dtors which GDB prefers over its
physname computed from class's DW_AT_name.
template<char c>
class C {
public:
void m () {}
~C() {}
};
typedef C<1> D;
D d;
int main () { d.m (); }
nm:
0000000000400604 W _ZN1CILc1EED1Ev
0000000000400604 W _ZN1CILc1EED2Ev
nm -C:
0000000000400604 W C<(char)1>::~C()
0000000000400604 W C<(char)1>::~C()
readelf -wi:
<1><3a>: Abbrev Number: 3 (DW_TAG_class_type)
<3b> DW_AT_name : (indirect string, offset: 0xac): C<'\001'>
The gcc-4.6 -> gcc-4.7 regression:
-PASS: gdb.cp/templates.exp: print destructor of template typedef
+FAIL: gdb.cp/templates.exp: print destructor of template typedef
(gdb) p D::~C
$1 = {void (C<(char)'\001'> * const)} 0x40056e <C<(char)'\001'>::~C()>
->
There is no field named ~C
reply other threads:[~2011-12-23 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-51668-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).