From: Alan Modra <amodra@gmail.com>
To: "Radouch, Zdenek" <zradouch@irobot.com>
Cc: "Paul_Koning@Dell.com" <Paul_Koning@Dell.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: extract ELF load address with binutils?
Date: Tue, 18 Mar 2014 23:44:00 -0000 [thread overview]
Message-ID: <20140318234418.GC9145@bubble.grove.modra.org> (raw)
In-Reply-To: <7ADBB2DB4DC7CF4CB641E9ADA826E5E2E1FC207A@hq-mbx-02.wardrobe.irobot.com>
On Tue, Mar 18, 2014 at 05:44:11PM +0000, Radouch, Zdenek wrote:
> But as I (and objcopy) have illustrated:
> 1. Not all LOAD types get loaded
Correct, only those with p_filsiz (readelf -l FileSize column)
non-zero. p_memsiz specifies a bss type area that is usually cleared
to zero by a program loader.
> 2. The address where the segment is loaded can be "wrong", when the loaded segment
> has been padded.
The address you showed isn't due to padding. You're seeing 0x158000
when .text starts at 0x15f000 because you linked the object for
dynamic paging with a page size of 0x8000. That imposes constraints
on p_vaddr. You will also be loading the ELF file header and program
headers, which may not be what you want.. See ld -n and ld -N
options.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2014-03-18 23:44 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
2014-03-18 17:44 ` Radouch, Zdenek
2014-03-18 23:44 ` Alan Modra [this message]
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=20140318234418.GC9145@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=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).