[Bug c++/16957] New: gdb segfaults when loading symbols in C++11-enabled application

[Bug c++/16957] New: gdb segfaults when loading symbols in C++11-enabled application

[0xd34df00d at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

            Bug ID: 16957
           Summary: gdb segfaults when loading symbols in C++11-enabled
                    application
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: 0xd34df00d at gmail dot com

Created attachment 7607
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7607&action=edit
Somewhat minimal reproducing example.

gdb-7.7.{0,1} segfaults for me when trying to debug my application. Debugging
gdb with gdb shows this trace inside gdb (only top 19 lines are shown, next
thousands of them are the same, I'd guess an infinite recursion):

(gdb) run ./main
Starting program: /usr/bin/gdb ./main
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
GNU gdb (Gentoo 7.7.1 p1) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./main...
Program received signal SIGSEGV, Segmentation fault.
d_print_comp (dpi=dpi@entry=0x7fffffffac00, options=options@entry=259,
dc=0x7fffffffb790) at ./cp-demangle.c:4721
4721    ./cp-demangle.c: Нет такого файла или каталога.
(gdb) bt
#0  d_print_comp (dpi=dpi@entry=0x7fffffffac00, options=options@entry=259,
dc=0x7fffffffb790) at ./cp-demangle.c:4721
#1  0x00000000007172c5 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=<optimized out>) at ./cp-demangle.c:4517
#2  0x0000000000717fae in d_print_comp (dpi=0x7fffffffac00, options=259,
dc=0x7fffffffb610) at ./cp-demangle.c:4730
#3  0x00000000007182c6 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb628) at ./cp-demangle.c:4911
#4  0x000000000071b4cf in d_print_function_type (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, mods=0x0, dc=0x7fffffffb640) at ./cp-demangle.c:5605
#5  0x0000000000717432 in d_print_comp (dpi=0x7fffffffac00, options=259,
dc=0x7fffffffb640) at ./cp-demangle.c:4796
#6  0x00000000007182c6 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb658) at ./cp-demangle.c:4911
#7  0x0000000000717241 in d_print_comp (dpi=0x7fffffffac00, options=259,
dc=0x7fffffffb670) at ./cp-demangle.c:4481
#8  0x00000000007182c6 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb688) at ./cp-demangle.c:4911
#9  0x00000000007190f2 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb580) at ./cp-demangle.c:4923
#10 0x0000000000717241 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb6a0) at ./cp-demangle.c:4481
#11 0x0000000000719d14 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb700) at ./cp-demangle.c:4781
#12 0x000000000071a2a5 in d_print_comp (dpi=0x7fffffffac00, options=259,
dc=0x7fffffffb718) at ./cp-demangle.c:4422
#13 0x0000000000717099 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb778) at ./cp-demangle.c:4312
#14 0x0000000000717fae in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb790) at ./cp-demangle.c:4730
#15 0x00000000007172c5 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=<optimized out>) at ./cp-demangle.c:4517
#16 0x0000000000717fae in d_print_comp (dpi=0x7fffffffac00, options=259,
dc=0x7fffffffb610) at ./cp-demangle.c:4730
#17 0x00000000007182c6 in d_print_comp (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, dc=0x7fffffffb628) at ./cp-demangle.c:4911
#18 0x000000000071b4cf in d_print_function_type (dpi=dpi@entry=0x7fffffffac00,
options=options@entry=259, mods=0x0, dc=0x7fffffffb640) at ./cp-demangle.c:5605

Unfortunately, I am not able to provide a small enough minimal reproducing
example, only the included archive reproduces the crash for me. In order to
build it one needs Qt4, building is like (assuming gcc 4.8 or newer):

g++ -std=c++11 -I /usr/include/qt4/ -I /usr/include/qt4/QtCore/ -I
/usr/include/qt4/QtSql/ -L/usr/lib/qt4 -lQtCore -lQtSql -O0 -g -ggdb main.cpp
-o main

or

clang++ -std=c++11 -I /usr/include/qt4/ -I /usr/include/qt4/QtCore/ -I
/usr/include/qt4/QtSql/ -DQ_COMPILER_INITIALIZER_LISTS -L/usr/lib/qt4 -lQtCore
-lQtSql -O0 -g -ggdb main.cpp -o main

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-15737-listarch-gdb-prs=sources.redhat.com@sourceware.org Sat May 17 18:56:56 2014
Return-Path: <gdb-prs-return-15737-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 3442 invoked by alias); 17 May 2014 18:56:55 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 3411 invoked by uid 48); 17 May 2014 18:56:55 -0000
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled
 application
Date: Sat, 17 May 2014 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.7
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: keiths at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-16957-4717-tNtLuLPpCr@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16957-4717@http.sourceware.org/bugzilla/>
References: <bug-16957-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00243.txt.bz2
Content-length: 603

https://sourceware.org/bugzilla/show_bug.cgi?id\x16957

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> ---
Looks like another demangler crash. Uncertain if it exactly c++/16752, but it
could be the same bug(s). Can you try the patch referenced in that bug?

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[0xd34df00d at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #2 from Georg Rudoy <0xd34df00d at gmail dot com> ---
(In reply to Keith Seitz from comment #1)
> Looks like another demangler crash. Uncertain if it exactly c++/16752, but
> it could be the same bug(s). Can you try the patch referenced in that bug?

The one in https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00404.html ? I'll try,
but that'll take some time.

In the meanwhile I've run the mangled strings from the test cases via c++filt,
and nothing got stuck or crashed. Does it make sense or help a bit?

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[keiths at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #3 from Keith Seitz <keiths at redhat dot com> ---
Yes, that looks like the patch.

If c++filt came pre-installed by your system, you're not likely to trigger the
bug -- it is almost certainly using a different libiberty than the one bundled
into gdb-binutils, but passing the system c++filt is very good supporting
evidence to suggest that you're running into the same bug.

Give the patch a try. (or just checkout gdb repo or download a snapshot)

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[0xd34df00d at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #4 from Georg Rudoy <0xd34df00d at gmail dot com> ---
Yes, that's c++filt that came with system binutils package.

Now I'm slightly confused. That's the patch for gdb then? If so, that's good,
as I was going to recompile gcc/binutils.

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[keiths at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #5 from Keith Seitz <keiths at redhat dot com> ---
GCC is considered the master repository for libiberty. gdb-binutils contains a
copy. So all you need to do is rebuild gdb.

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[0xd34df00d at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #6 from Georg Rudoy <0xd34df00d at gmail dot com> ---
Great, thanks for the explanation!

The patch didn't work, though. gdb still crashes with exactly the same
backtrace.

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[gbenson at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Gary Benson <gbenson at redhat dot com> changed:

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

--- Comment #7 from Gary Benson <gbenson at redhat dot com> ---
Georg, could you please rebuild GDB with this patch: http://tinyurl.com/k2c6mw4
It will catch the crash and print the offending symbol.

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[gbenson at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #8 from Gary Benson <gbenson at redhat dot com> ---
Georg, alternatively can you supply more of the backtrace of a crash?  I need
to see the mangled symbol name.  http://gbenson.net/?p=422 shows an example,
frames 9-12 have the mangled symbol mangled=0x7ffffac19ea0 "_Z1-Av23*;cG~Wo2Vu"

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[0xd34df00d at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #9 from Georg Rudoy <0xd34df00d at gmail dot com> ---
(In reply to Gary Benson from comment #8)
> Georg, alternatively can you supply more of the backtrace of a crash?  I
> need to see the mangled symbol name.  http://gbenson.net/?p=422 shows an
> example, frames 9-12 have the mangled symbol mangled=0x7ffffac19ea0
> "_Z1-Av23*;cG~Wo2Vu"

Thanks, that's much faster than rebuilding with a patch. The line in backtrace
containing d_demangle_callback:

#69765 0x000000000071e518 in d_demangle_callback (mangled=<optimized out>,
mangled@entry=0xe01eb4
"_Z7ZipWithI7QStringS0_5QListZN4oral6detail16AdaptCreateTableI7AccountEES0_RKNS3_16CachedFieldsDataEEUlRKS0_SA_E_ET1_IDTclfp1_cvT__EcvT0__EEEERKT1_ISC_ERKT1_ISD_ET2_",
options=259, callback=callback@entry=0x716e70
<d_growable_string_callback_adapter>, opaque=opaque@entry=0x7fffffffd550) at
./cp-demangle.c:5890

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[gbenson at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #10 from Gary Benson <gbenson at redhat dot com> ---
Confirmed and filed as:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61233

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[palves at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Pedro Alves <palves at redhat dot com> changed:

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

--- Comment #11 from Pedro Alves <palves at redhat dot com> ---
gcc/demangler patch sent:
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02279.html

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

[Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled application

[bap.fayol at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

yaoltreza <bap.fayol at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bap.fayol at gmail dot com

--- Comment #14 from yaoltreza <bap.fayol at gmail dot com> ---
thank you for the information. https://www.vitrier-strasbourg.com

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