public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sourceware at ca dot sh13.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17157] GDB segfault when demangling symbol
Date: Fri, 12 Dec 2014 20:08:00 -0000	[thread overview]
Message-ID: <bug-17157-4717-X2TbX358mx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17157-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from sourceware at ca dot sh13.net ---
Ok, this problem is a bit more complicated. First, a newer GCC (4.9.1) and
Clang 3.5 doesn't produce the symbol any more. Running a more recent c++filt on
it now crashes c++filt -- if you look closely, the originally demangled type
was also incorrect, as: decltype (((float)()*(float)())) does not make sense --
should have been decltype (float ()*float ()) which is simply float.

I'm debugging a new crash now where the demangler/libiberty starts producing a
symbol name with decltype in it, which I strongly suspect is similar to the
original issue. Am I right to assume that decltype is never part of a mangled
symbol name?

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


  parent reply	other threads:[~2014-12-12 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 18:24 [Bug gdb/17157] New: " sourceware at ca dot sh13.net
2014-07-15  8:39 ` [Bug gdb/17157] " gbenson at redhat dot com
2014-12-12 20:08 ` sourceware at ca dot sh13.net [this message]
2014-12-19 13:04 ` gbenson at redhat dot com
2024-01-02 16:18 ` ssbssa at sourceware dot org

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-17157-4717-X2TbX358mx@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).