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++/15801] some C++11 symbols can't be demangled
Date: Tue, 30 Jul 2013 01:46:00 -0000	[thread overview]
Message-ID: <bug-15801-4717-3cDsxZLuIP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15801-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15801

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |keiths at redhat dot com

--- Comment #1 from Keith Seitz <keiths at redhat dot com> ---
The two examples given demangle for me using 7.6.50.20130729-cvs, and they both
demangle identically to the Fedora 18 system c++filt (version
2.23.51.0.1-6.fc18 20120806):

$ ./gdb -nx -q
(gdb) set lang c++
(gdb) maint demangle
_Z7extractILc9ELi0EEbN7strings7XStringE6RecordIXT_EXT0_EJEE
bool extract<(char)9, 0>(strings::XString, Record<(char)9, 0>)
(gdb) maint demangle _Z1gIJidEEDTclL_Z1fEspplfp_Li1EEEDpT_
decltype (f(({parm#1}+(1))...)) g<int, double>(int, double)

In fact, I tried the 7.6 branch, and that, too, works the same way. So there is
something unique to your situation that is causing you problems. Do you have a
test case that you can share?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2013-07-30  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  1:06 [Bug c++/15801] New: " b.r.longbons at gmail dot com
2013-07-30  1:46 ` keiths at redhat dot com [this message]
2013-07-30  5:04 ` [Bug c++/15801] " b.r.longbons at gmail dot com
2013-07-30  5:57 ` b.r.longbons at gmail dot com
2013-08-01  5:53 ` b.r.longbons at gmail dot com
2022-12-23 19:20 ` 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-15801-4717-3cDsxZLuIP@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).