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++/14998] GDB cannot handle pointer to member functions being encoded with DW_TAG_ptr_to_member_type
Date: Mon, 07 Jan 2013 19:01:00 -0000 [thread overview]
Message-ID: <bug-14998-4717-llmFQDMM7F@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14998-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14998
--- Comment #6 from Tom Tromey <tromey at redhat dot com> 2013-01-07 19:01:17 UTC ---
This .s seems a little weird to me, but maybe I am confused.
When I look at the DWARF I see:
<1><47>: Abbrev Number: 6 (DW_TAG_ptr_to_member_type)
<48> DW_AT_type : <0x34>
<4c> DW_AT_containing_type: <0x3f>
which points to
<1><34>: Abbrev Number: 3 (DW_TAG_subroutine_type)
<35> DW_AT_type : <0x26>
<2><39>: Abbrev Number: 4 (DW_TAG_formal_parameter)
<3a> DW_AT_type : <0x2d>
0x2d is just
<1><2d>: Abbrev Number: 2 (DW_TAG_base_type)
<2e> DW_AT_name : (indirect string, offset: 0x46): float
<32> DW_AT_encoding : 4 (float)
<33> DW_AT_byte_size : 4
I was expecting the subroutine type to have an artificial parameter
for the "this" pointer.
I think if that was added then calling would work.
Printing the artificial argument appears to be a conscious decision.
>From c-typeprint.c:
Artificial arguments, such as "this"
in non-static methods, are displayed if LINKAGE_NAME is zero
I think this is a bit weird though. I wouldn't mind changing it or
perhaps adding a ptype flag to control it.
--
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:[~2013-01-07 19:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 1:10 [Bug c++/14998] New: " dblaikie at gmail dot com
2013-01-07 15:41 ` [Bug c++/14998] " tromey at redhat dot com
2013-01-07 17:11 ` tromey at redhat dot com
2013-01-07 17:57 ` dblaikie at gmail dot com
2013-01-07 17:58 ` dblaikie at gmail dot com
2013-01-07 17:59 ` dblaikie at gmail dot com
2013-01-07 19:01 ` tromey at redhat dot com [this message]
2013-01-07 19:11 ` dblaikie at gmail dot com
2013-01-07 19:35 ` tromey at redhat dot com
2013-01-07 19:41 ` dblaikie at gmail dot com
2013-01-08 3:08 ` dblaikie at gmail dot com
2013-01-08 4:48 ` tromey at redhat dot com
2013-01-08 17:12 ` tromey at redhat dot com
2013-01-19 19:22 ` dblaikie at gmail dot com
2013-01-31 17:41 ` cvs-commit at gcc dot gnu.org
2013-01-31 17:42 ` tromey 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-14998-4717-llmFQDMM7F@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).