From: Daniel Jacobowitz <dan@codesourcery.com>
To: Matt Fischer <mattfischer84@gmail.com>, binutils@sourceware.org
Subject: Re: Load addresses for ELF program headers on ARM
Date: Mon, 11 Oct 2010 02:50:00 -0000 [thread overview]
Message-ID: <20101011024959.GA22531@caradoc.them.org> (raw)
In-Reply-To: <20101011015506.GM26553@bubble.grove.modra.org>
On Mon, Oct 11, 2010 at 12:25:06PM +1030, Alan Modra wrote:
> On Sun, Oct 10, 2010 at 07:46:58PM -0500, Matt Fischer wrote:
> > The linker created two program headers, one for TEXT, and one for
> > DATA. The TEXT one looks fine--both vaddr and paddr are at 0. The
> > DATA segment, however, has a problem. It's been given a vaddr of
> > 0x10000000, and a paddr of 0x000000b4. The former is the section's
> > relocation address, and the latter is its load address. However, the
> > ARM spec for ELF states that segments should have vaddr set to their
> > load address, and paddr set to 0.
>
> Which ARM ELF spec are you talking about? An old and buggy one, I'd
> guess. If the one you're looking at says that it is clearly in
> conflict with the parent SysV ELF ABI spec. This spec
> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044b/IHI0044B_aaelf.pdf
> is silent on p_vaddr and p_paddr.
My memory on this is a bit vague, but I think that the ARM debugger
does behave as Matt described (or used to). You should be able to
post-process the file, either with objcopy or a custom utility; it
will be a simple one.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-10-11 2:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 0:47 Matt Fischer
2010-10-11 1:55 ` Alan Modra
2010-10-11 2:43 ` Matt Fischer
2010-10-11 3:29 ` Alan Modra
2010-10-11 3:39 ` Matt Fischer
2010-10-11 14:44 ` Daniel Jacobowitz
2010-10-11 15:21 ` Matt Fischer
2011-03-15 15:36 ` Matt Fischer
2011-03-16 4:29 ` Alan Modra
2011-03-17 0:37 ` Matt Fischer
2011-03-17 2:38 ` Alan Modra
2011-03-17 2:56 ` Matt Fischer
2010-10-11 2:50 ` Daniel Jacobowitz [this message]
2010-10-11 3:28 ` Matt Fischer
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=20101011024959.GA22531@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=mattfischer84@gmail.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).