public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "b.r.longbons at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15801] New: some C++11 symbols can't be demangled
Date: Tue, 30 Jul 2013 01:06:00 -0000	[thread overview]
Message-ID: <bug-15801-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15801
           Summary: some C++11 symbols can't be demangled
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: b.r.longbons at gmail dot com

When debugging my program, I noticed that several symbols in a recursive
template failed. The simplest one is:
_Z7extractILc9ELi0EEbN7strings7XStringE6RecordIXT_EXT0_EJEE

I noticed a similar case in libiberty test data:
_Z1gIJidEEDTclL_Z1fEspplfp_Li1EEEDpT_

Talking directly to libiberty, my symbol also demangles. I have not observed
any difference between my symbol and that one.

The test entry specifies gnu-v3 (I haven't found any documentation on how that
is different than gnu - older or newer?), but (gdb) set demangle-style gnu-v3
does not make maintenance demangle accept it.

I have not observed any difference between gdb 7.6 and gdb trunk.

Note: the c++filt program, which is part of binutils, learned to understand the
symbol sometime between 2.22 and 2.23

Incidentally, this bug is an *excellent* argument for why static libraries
(and/or copylibs) need to die.

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


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

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