From: <Paul_Koning@Dell.com>
To: <zradouch@irobot.com>
Cc: <binutils@sourceware.org>
Subject: Re: extract ELF load address with binutils?
Date: Tue, 18 Mar 2014 17:13:00 -0000 [thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD16C83E5D@AUSX10MPC103.AMER.DELL.COM> (raw)
In-Reply-To: <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FC2052@hq-mbx-02.wardrobe.irobot.com>
On Mar 18, 2014, at 1:02 PM, Radouch, Zdenek <zradouch@irobot.com> wrote:
> I am writing a firmware updater that takes an ELF executable and needs to extract the RAM data
> and the address to where the data should be loaded. ...
> The question is can I somehow convince one of the binutils to give me the load address alone,
> so that I don't have to invent an algorithm extracting the address from the section dump?
I’m not sure the notion of “THE load address” makes sense. It may be valid for your specific case, but not in general. ELF files can have multiple load sections, each of which has a load address.
Normally I would say: look in the program headers. Each header of type LOAD describes something that’s loaded, and it shows the addresses.
paul
next prev parent reply other threads:[~2014-03-18 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7ADBB2DB4DC7CF4CB641E9ADA826E5E2AAC571BC@HQ-MBX-01.wardrobe.irobot.com>
[not found] ` <m3a9i3s8s1.fsf@pepe.airs.com>
[not found] ` <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FBDF7F@hq-mbx-02.wardrobe.irobot.com>
[not found] ` <m3siqgw32g.fsf@pepe.airs.com>
[not found] ` <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FC0FF6@hq-mbx-02.wardrobe.irobot.com>
[not found] ` <m3k3brwvew.fsf@pepe.airs.com>
2014-03-18 17:02 ` Radouch, Zdenek
2014-03-18 17:13 ` Paul_Koning [this message]
2014-03-18 17:44 ` Radouch, Zdenek
2014-03-18 23:44 ` Alan Modra
2014-03-19 12:05 ` Radouch, Zdenek
2014-03-19 13:24 ` Erik Christiansen
2014-03-20 18:12 ` Radouch, Zdenek
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=C75A84166056C94F84D238A44AF9F6AD16C83E5D@AUSX10MPC103.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=binutils@sourceware.org \
--cc=zradouch@irobot.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).