public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Craig Jeffree <craig.jeffree@preston.net>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: <incomplete type>
Date: Mon, 29 Aug 2005 07:50:00 -0000	[thread overview]
Message-ID: <1125301769.10500.124.camel@norman> (raw)
In-Reply-To: <m3acj45xnv.fsf@alligator.red-bean.com>

On Fri, 2005-08-26 at 12:02 -0700, Jim Blandy wrote:
> 'readelf -wi' dumps Dwarf debugging info in a human-readable form.
> You can apply it to relocatable object files, executables, and shared
> libraries.  You probably want to apply it to the executable or shared
> library, since that's fewer steps removed from GDB, but the output
> will be large.  You'll need to search for a DW_TAG_structure debugging
> information entry ("die") whose DW_AT_name attribute is the mangled
> form of Soi::Waypoint, and verify that the members are indeed listed
> there.  If you could post that die when you find it, that might be
> interesting.
> 
I don't think I really understand what I'm looking at here.  In the .o
file I found this:
 <1><ee6b>: Abbrev Number: 113 (DW_TAG_structure_type)
     DW_AT_sibling     : <f3d6>
     DW_AT_name        : (indirect string, offset: 0xd7e3): Waypoint
     DW_AT_byte_size   : 120
     DW_AT_decl_file   : 62
     DW_AT_decl_line   : 33
     DW_AT_containing_type: <1668a>

and in the executable I found this:
 <2><3bb78>: Abbrev Number: 2 (DW_TAG_structure_type)
     DW_AT_sibling     : <3bc2e>
     DW_AT_name        : (indirect string, offset: 0x4ff824): Waypoint
     DW_AT_byte_size   : 24
     DW_AT_decl_file   : 123
     DW_AT_decl_line   : 90


Are these complete dies?  They obviously don't seem to contain any
members or have any references to anything else except for the sibling
which is just an unrelated DW_TAG_structure_type.  Scanning through the
information none of the dies appears to contain anything that look like
members, however the members appear in their own right as separate dies
in the executable but not in the .o file like this:

 <2><a6859d9>: Abbrev Number: 71 (DW_TAG_member)
     DW_AT_name        : (indirect string, offset: 0x7724ea): wpname_
     DW_AT_decl_file   : 158
     DW_AT_decl_line   : 58
     DW_AT_type        : <a667ae0>
     DW_AT_data_member_location: 2 byte block: 23 10
(DW_OP_plus_uconst: 16)
     DW_AT_accessibility: 3     (private)


Am I on the right track, how are the members described in the dies?

Thanks for the help,
Craig.

  reply	other threads:[~2005-08-29  7:50 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 [this message]
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
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=1125301769.10500.124.camel@norman \
    --to=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).