public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "avi@cloudius-systems.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/17455] New: gdb segfaults while demangling Date: Sun, 05 Oct 2014 12:37:00 -0000 [thread overview] Message-ID: <bug-17455-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2014-10-05 12:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-05 12:37 avi@cloudius-systems.com [this message] 2014-10-05 12:43 ` [Bug c++/17455] " avi@cloudius-systems.com 2014-10-06 9:37 ` gbenson at redhat dot com 2014-10-06 9:39 ` gbenson at redhat dot com 2015-03-24 12:45 ` jeanmichael.celerier at gmail dot com
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-17455-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: linkBe 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).