From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dave Brolley <brolley@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: SID ELF loader using wrong load address?
Date: Mon, 04 Feb 2002 12:42:00 -0000 [thread overview]
Message-ID: <20020204154227.J10856@redhat.com> (raw)
In-Reply-To: <3C5EEF5F.77116D06@redhat.com>; from brolley@redhat.com on Mon, Feb 04, 2002 at 03:30:23PM -0500
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
Hi -
brolley wrote:
> [...]
> This is a section of code which should be loaded at the end of the .text
> section and is intended to be copied (by the application itself) to
> address 0x1000 before being executed. However, the SID ELF loader
> currently loads this section at address 0x1000 (the VMA) instead of at
> the given LMA. [...]
Good catch, thanks! Looking at include/elf/external.h, I guess we want
Elf32_External_Phdr.p_paddr instead of p_vaddr.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-04 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 12:30 Dave Brolley
2002-02-04 12:42 ` Frank Ch. Eigler [this message]
2002-02-04 14:33 ` Dave Brolley
2002-02-05 8:39 ` Dave Brolley
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=20020204154227.J10856@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=sid@sources.redhat.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).