public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dblaikie at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/16843] GDB relies on the mangled name of a subprogram to be a prefix of the enclosing class name
Date: Tue, 15 Apr 2014 20:43:00 -0000 [thread overview]
Message-ID: <bug-16843-4717-tSkPOQvFMl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16843-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16843
--- Comment #2 from David Blaikie <dblaikie at gmail dot com> ---
(In reply to Gary Benson from comment #1)
> David, I don't have a copy of Clang to hand. Could you run nm on the object
> files you have generated with GCC and Clang and paste the mangled symbol
> names here please?
Hmm, I'm not sure if that's relevant (I'm wondering if perhaps I did a poor job
explaining the problem - or I just don't understand it at all), but the default
output of "nm" for the two object files no matter whether they're compiled with
GCC or Clang is:
src1.cpp:
0000000000000000 T _Z4funcv
0000000000000000 W _ZN3fooILc1EE3memEv
0000000000000000 b _ZZ4funcvE1f
src2.cpp:
U _Z4funcv
0000000000000000 T main
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-15 20:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 22:20 [Bug c++/16843] New: " dblaikie at gmail dot com
2014-04-15 11:06 ` [Bug c++/16843] " gbenson at redhat dot com
2014-04-15 11:16 ` gbenson at redhat dot com
2014-04-15 20:43 ` dblaikie at gmail dot com [this message]
2014-06-25 20:00 ` tromey at redhat dot com
2022-10-21 17:54 ` tromey at sourceware dot org
2022-10-21 20:24 ` dblaikie at gmail dot com
2024-04-10 9:59 ` tromey at sourceware dot org
2024-04-18 22:08 ` tromey at sourceware dot org
2024-05-14 20:00 ` cvs-commit at gcc dot gnu.org
2024-05-14 20:01 ` tromey at sourceware dot 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-16843-4717-tSkPOQvFMl@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).