From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24485 invoked by alias); 17 May 2014 17:49:36 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 24459 invoked by uid 48); 17 May 2014 17:49:35 -0000 From: "0xd34df00d at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/16957] New: gdb segfaults when loading symbols in C++11-enabled application Date: Sat, 17 May 2014 17:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: 0xd34df00d at gmail 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q2/txt/msg00242.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D16957 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=3D7607&action=3Dedit Somewhat minimal reproducing example. gdb-7.7.{0,1} segfaults for me when trying to debug my application. Debuggi= ng 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 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: . Find the GDB manual and other documentation resources online at: . 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=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D2= 59, dc=3D0x7fffffffb790) at ./cp-demangle.c:4721 4721 ./cp-demangle.c: =D0=9D=D0=B5=D1=82 =D1=82=D0=B0=D0=BA=D0=BE=D0=B3= =D0=BE =D1=84=D0=B0=D0=B9=D0=BB=D0=B0 =D0=B8=D0=BB=D0=B8 =D0=BA=D0=B0=D1=82= =D0=B0=D0=BB=D0=BE=D0=B3=D0=B0. (gdb) bt #0 d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry= =3D259, dc=3D0x7fffffffb790) at ./cp-demangle.c:4721 #1 0x00000000007172c5 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D) at ./cp-demangle.c:4517 #2 0x0000000000717fae in d_print_comp (dpi=3D0x7fffffffac00, options=3D259, dc=3D0x7fffffffb610) at ./cp-demangle.c:4730 #3 0x00000000007182c6 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb628) at ./cp-demangle.c:4911 #4 0x000000000071b4cf in d_print_function_type (dpi=3Ddpi@entry=3D0x7fffff= ffac00, options=3Doptions@entry=3D259, mods=3D0x0, dc=3D0x7fffffffb640) at ./cp-dem= angle.c:5605 #5 0x0000000000717432 in d_print_comp (dpi=3D0x7fffffffac00, options=3D259, dc=3D0x7fffffffb640) at ./cp-demangle.c:4796 #6 0x00000000007182c6 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb658) at ./cp-demangle.c:4911 #7 0x0000000000717241 in d_print_comp (dpi=3D0x7fffffffac00, options=3D259, dc=3D0x7fffffffb670) at ./cp-demangle.c:4481 #8 0x00000000007182c6 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb688) at ./cp-demangle.c:4911 #9 0x00000000007190f2 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb580) at ./cp-demangle.c:4923 #10 0x0000000000717241 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb6a0) at ./cp-demangle.c:4481 #11 0x0000000000719d14 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb700) at ./cp-demangle.c:4781 #12 0x000000000071a2a5 in d_print_comp (dpi=3D0x7fffffffac00, options=3D259, dc=3D0x7fffffffb718) at ./cp-demangle.c:4422 #13 0x0000000000717099 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb778) at ./cp-demangle.c:4312 #14 0x0000000000717fae in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb790) at ./cp-demangle.c:4730 #15 0x00000000007172c5 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D) at ./cp-demangle.c:4517 #16 0x0000000000717fae in d_print_comp (dpi=3D0x7fffffffac00, options=3D259, dc=3D0x7fffffffb610) at ./cp-demangle.c:4730 #17 0x00000000007182c6 in d_print_comp (dpi=3Ddpi@entry=3D0x7fffffffac00, options=3Doptions@entry=3D259, dc=3D0x7fffffffb628) at ./cp-demangle.c:4911 #18 0x000000000071b4cf in d_print_function_type (dpi=3Ddpi@entry=3D0x7fffff= ffac00, options=3Doptions@entry=3D259, mods=3D0x0, dc=3D0x7fffffffb640) at ./cp-dem= angle.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=3Dc++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.c= pp -o main or clang++ -std=3Dc++11 -I /usr/include/qt4/ -I /usr/include/qt4/QtCore/ -I /usr/include/qt4/QtSql/ -DQ_COMPILER_INITIALIZER_LISTS -L/usr/lib/qt4 -lQtC= ore -lQtSql -O0 -g -ggdb main.cpp -o main --=20 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: 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: List-Subscribe: List-Archive: List-Post: List-Help: , 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" 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: In-Reply-To: References: 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=16957 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz --- 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.