public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "0xd34df00d at gmail 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 19:09:00 -0000 [thread overview]
Message-ID: <bug-16957-4717-WklulfbOi8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16957-4717@http.sourceware.org/bugzilla/>
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.
next prev parent reply other threads:[~2014-05-17 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 17:49 [Bug c++/16957] New: " 0xd34df00d at gmail dot com
2014-05-17 19:09 ` 0xd34df00d at gmail dot com [this message]
2014-05-17 19:21 ` [Bug c++/16957] " keiths at redhat dot com
2014-05-17 19:24 ` 0xd34df00d at gmail dot com
2014-05-17 19:27 ` keiths at redhat dot com
2014-05-17 20:01 ` 0xd34df00d at gmail dot com
2014-05-19 9:41 ` gbenson at redhat dot com
2014-05-19 9:43 ` gbenson at redhat dot com
2014-05-19 12:53 ` 0xd34df00d at gmail dot com
2014-05-19 14:04 ` gbenson at redhat dot com
2014-05-27 12:10 ` palves at redhat dot com
2021-10-21 6:49 ` bap.fayol 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-16957-4717-WklulfbOi8@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: link
Be 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).