[Bug c++/17455] New: gdb segfaults while demangling

[Bug c++/17455] New: gdb segfaults while demangling

[avi@cloudius-systems.com]

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

            Bug ID: 17455
           Summary: gdb segfaults while demangling
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: avi@cloudius-systems.com

The following symbol crashes both gdb and c++filt:

_ZSt1aIRPZN1bII1cIcEEE1dIZN1eIIS2_EE1fEOS3_EUlRT_E_EEvOT_E1gEOS8_RNSt1hIS8_E1iE

gdb seems to enter an endless recursion loop, from which it only exits when it
overflows its stack.

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

[Bug c++/17455] gdb segfaults while demangling

[avi@cloudius-systems.com]

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

--- Comment #1 from Avi Kivity <avi@cloudius-systems.com> ---
Seems to be triggered by calling a function with a C++ generalized lambda as a
parameter:

f([...] (auto& ) { ... }) -> fail
f([...] (the_real_type&) { ... }) -> success

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

[Bug c++/17455] gdb segfaults while demangling

[gbenson at redhat dot com]

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

Gary Benson <gbenson at redhat dot com> changed:

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

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

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

[Bug c++/17455] gdb segfaults while demangling

[gbenson at redhat dot com]

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

--- Comment #3 from Gary Benson <gbenson at redhat dot com> ---
Note that the very latest versions of GDB are able to recover from demangler
crashes.

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

[Bug c++/17455] gdb segfaults while demangling

[jeanmichael.celerier at gmail dot com]

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

Jean-Michaël Celerier <jeanmichael.celerier at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeanmichael.celerier@gmail.
                   |                            |com

--- Comment #4 from Jean-Michaël Celerier <jeanmichael.celerier at gmail dot com> ---
I get a similar crash with the following symbol :

_ZSt4moveIRZN5coppa8oscquery15WebSocketClientC1INS1_12RemoteDevice8m_clientMUlDpOT_E_EEEOT_EUlSt8weak_ptrIvEE_EONSt16remove_referenceIS9_E4typeESA_

The code is compiled with clang-3.6, and both gdb-7.9, lldb-3.6, and
c++filt-2.25.0 choke on the symbol.

When debugging c++filt with gdb, it seems like the infinite recursion is in
libbfd.so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-17714-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Mar 24 12:45:22 2015
Return-Path: <gdb-prs-return-17714-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 16845 invoked by alias); 24 Mar 2015 12:45:21 -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 16794 invoked by uid 55); 24 Mar 2015 12:45:16 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16466] -break-insert and -dprintf-insert do not
 remember a specified thread for a pending breakpoint
Date: Tue, 24 Mar 2015 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: antoine.tremblay at ericsson dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16466-4717-gToUzYKXJJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16466-4717@http.sourceware.org/bugzilla/>
References: <bug-16466-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: 2015-q1/txt/msg00479.txt.bz2
Content-length: 1624

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Antoine Tremblay <hexa@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h\x15630549010233e9d0f0b1971d27e121cd74bdd0

commit 15630549010233e9d0f0b1971d27e121cd74bdd0
Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Date:   Thu Feb 19 15:23:34 2015 -0500

    Fix breakpoint thread condition missing with mi and a pending breakpoint.

    When setting a pending breakpoint with a thread condition while using
    the mi interface, the thread condition would be lost by gdb when the
breakpoint
    was resolved.

    This patch fixes this behavior by setting the thread condition properly in
the
    mi case.

    Also, this patch modifies the mi-pending test case to test for this issue
and
    removes some unneeded code in the testcase and dependency on stdio.

    gdb/Changelog:
        PR breakpoints/16466
        * breakpoint.c (create_breakpoint): Set thread on breakpoint struct.

    gdb/testsuite/ChangeLog:
        PR breakpoints/16466
        * gdb.mi/Makefile.in: Add mi-pendshr2.sl to cleanup.
        * gdb.mi/mi-pending.c (thread_func): New function.
        (int main): Add threading support required.
        * gdb.mi/mi-pending.exp: Add tests for this issue.
        * gdb.mi/mi-pendshr.c (pendfunc1): Remove stdio dependency.
        (pendfunc2): Remove stdio dependency.
        * gdb.mi/mi-pendshr2.c: New file.

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