This is the mail archive of the
mailing list for the binutils project.
Re: extract ELF load address with binutils?
- From: <Paul_Koning at Dell dot com>
- To: <zradouch at irobot dot com>
- Cc: <binutils at sourceware dot org>
- Date: Tue, 18 Mar 2014 17:12:30 +0000
- Subject: Re: extract ELF load address with binutils?
- Authentication-results: sourceware.org; auth=none
- References: <7ADBB2DB4DC7CF4CB641E9ADA826E5E2AAC571BC at HQ-MBX-01 dot wardrobe dot irobot dot com> <m3a9i3s8s1 dot fsf at pepe dot airs dot com> <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FBDF7F at hq-mbx-02 dot wardrobe dot irobot dot com> <m3siqgw32g dot fsf at pepe dot airs dot com> <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FC0FF6 at hq-mbx-02 dot wardrobe dot irobot dot com> <m3k3brwvew dot fsf at pepe dot airs dot com> <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FC2052 at hq-mbx-02 dot wardrobe dot irobot dot com>
On Mar 18, 2014, at 1:02 PM, Radouch, Zdenek <email@example.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.