From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Craig Jeffree <craig.jeffree@preston.net>, gdb@sources.redhat.com
Subject: Re: <incomplete type>
Date: Mon, 12 Sep 2005 01:35:00 -0000 [thread overview]
Message-ID: <20050912013539.GB10666@nevyn.them.org> (raw)
In-Reply-To: <m3k6i0uxp8.fsf@alligator.red-bean.com>
On Thu, Sep 01, 2005 at 05:20:51PM -0700, Jim Blandy wrote:
> >> (I'm apparently wrong about the DW_AT_name being mangled. Does the
> >> DW_AT_containing_type attribute of the first die point at something
> >> named "Soi"?)
> >
> > The containing type for 'Waypoint' points to a die that appears to
> > describe Waypoint's base class.
>
> That's odd. The Dwarf 3 spec only mentions DW_AT_containing_type in
> the context of dies describing pointer-to-member types. So the
> attribute wasn't what I guessed it was, but it also doesn't belong
> there.
This is a GNUism, and a very bad one nowadays, especially since GDB
relies on it. I have queued up behind my other pending DWARF patches
some fixes for that. For GCC, DW_AT_containing_type is the type
containing the class's vtable pointer.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-12 1:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 2:06 Craig Jeffree
2005-08-26 19:04 ` Jim Blandy
2005-08-29 7:50 ` Craig Jeffree
2005-08-29 18:38 ` Jim Blandy
2005-09-01 23:55 ` Craig Jeffree
2005-09-02 0:22 ` Jim Blandy
2005-09-02 1:50 ` Craig Jeffree
2005-09-02 13:16 ` Daniel Jacobowitz
2005-09-05 7:34 ` Craig Jeffree
2005-09-05 14:00 ` Daniel Jacobowitz
2005-09-06 7:15 ` Craig Jeffree
2005-09-12 1:34 ` Daniel Jacobowitz
2005-09-15 5:12 ` Craig Jeffree
2005-09-19 7:44 ` Craig Jeffree
2005-09-12 1:35 ` Daniel Jacobowitz [this message]
2005-09-02 2:05 ` Craig Jeffree
-- strict thread matches above, loose matches on Subject: below --
2005-05-01 21:21 "Incomplete Type" lin q
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=20050912013539.GB10666@nevyn.them.org \
--to=drow@false.org \
--cc=craig.jeffree@preston.net \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
/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).