From: Daniel Jacobowitz <drow@false.org>
To: Ivan Pantushev <ipantushev@iname.com>
Cc: gdb@sources.redhat.com
Subject: Re: Question about "gnu.linkonce.wi." sections
Date: Mon, 07 Nov 2005 13:41:00 -0000 [thread overview]
Message-ID: <20051107134146.GA2426@nevyn.them.org> (raw)
In-Reply-To: <20051107080553.C3FA584028@ws1-5.us4.outblaze.com>
[I feel like I've answered this question recently, but I can't remember
where...]
On Mon, Nov 07, 2005 at 03:05:53AM -0500, Ivan Pantushev wrote:
> <1><c2>: Abbrev Number: 6 (DW_TAG_array_type)
> DW_AT_sibling : <d2>
> DW_AT_type : <#19>
>
> The last DW_AT_type references type information at offset 0x19, but
> there is no such information in the .debug_info section.
#19 means that this is a reference to another compilation unit. You
are looking at an unlinked object file. That means that there are
unapplied relocations; take a look at the readelf -r output and you can
work out which section the relocation at that offset is targetting. If
there's no relocation, it's the current section.
Readelf doesn't have any way to print out relocations for dwarf
decoding. It is more effective on linked objects.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-07 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 8:06 Ivan Pantushev
2005-11-07 13:41 ` Daniel Jacobowitz [this message]
2005-11-07 14:32 Ivan Pantushev
2005-11-07 14:39 ` Daniel Jacobowitz
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=20051107134146.GA2426@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ipantushev@iname.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