From: Reid Linnemann <linnemannr@gmail.com>
To: Reid Linnemann <linnemannr@gmail.com>, binutils@sourceware.org
Subject: Re: bfd_get_section_size() returns zero?
Date: Thu, 17 Feb 2011 21:55:00 -0000 [thread overview]
Message-ID: <AANLkTi=tKT68fw02t4YUjdvE7ycV+LggJ3V9pOioG5Q9@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin7h8wwZhDXN_2OfAti93X28i06Qzf_kFAiFJJU@mail.gmail.com>
On Thu, Feb 17, 2011 at 9:32 AM, Reid Linnemann <linnemannr@gmail.com> wrote:
> On Wed, Feb 16, 2011 at 9:57 PM, Alan Modra <amodra@gmail.com> wrote:
>> Your most likely problem is that bfd headers don't match the bfd
>> library you are linking/running against.
>>
>> --
>> Alan Modra
>> Australia Development Lab, IBM
>>
>
> I'm fairly certain that's not the case. If it were I would still
> expect bfd_get_section_size() to return a valid value since libbfd
> would internally agree on the structure of the asection record. Would
> you agree?
>
> Is it generally accepted that fetching a section with
> bfd_get_section_by_name() will always yield an asection with size
> information? Or can lbbfd perform a "lazy load" that needs
> supplementary actions to fetch all information for the section? And
> what would those supplementary actions be?
>
> Thanks for your assistance,
> Reid
>
After enough rummaging around I found this:
https://bugzilla.redhat.com/show_bug.cgi?id=529028
Basically the bfd.h header was not matching the ABI, as was suspected.
prev parent reply other threads:[~2011-02-17 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 0:11 Reid Linnemann
2011-02-17 3:57 ` Alan Modra
2011-02-17 15:32 ` Reid Linnemann
2011-02-17 21:55 ` Reid Linnemann [this message]
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='AANLkTi=tKT68fw02t4YUjdvE7ycV+LggJ3V9pOioG5Q9@mail.gmail.com' \
--to=linnemannr@gmail.com \
--cc=binutils@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).