This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/15801] New: some C++11 symbols can't be demangled


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]