public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/14365] gdb crashes when checking ctor of lambdas (in is_ctor_or_dtor)
Date: Wed, 01 Aug 2012 18:55:00 -0000 [thread overview]
Message-ID: <bug-14365-4717-S9Ah8BrYg8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14365-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14365
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-08-01 18:55:14 UTC ---
I reproduced the bug.
I don't think this is the correct fix.
What seems to be happening here is that we are trying to
compute the physname for a type that is a pointer to a member
function of an unnamed structure type.
Because it is unnamed, c_type_print_base falls through to
printing the body of the structure, instead of its name.
This then crashes.
Maybe NULL checks in is_constructor_name and is_destructor_name
would be ok; though I am not sure. But even if those were there
we would still be seeing very weird results here.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-08-01 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 13:30 [Bug c++/14365] New: " marco.trevisan at canonical dot com
2012-07-14 13:35 ` [Bug c++/14365] " marco.trevisan at canonical dot com
2012-07-15 12:55 ` jan.kratochvil at redhat dot com
2012-08-01 18:55 ` tromey at redhat dot com [this message]
2012-08-01 18:58 ` tromey at redhat dot com
2012-08-03 17:22 ` keiths at redhat dot com
2012-08-19 19:38 ` cvs-commit at gcc dot gnu.org
2012-08-19 19:40 ` keiths at redhat 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-14365-4717-S9Ah8BrYg8@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).