From: David Vrabel <dvrabel@arcom.com>
To: Bert Thomas <bert@brothom.nl>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: bug in RedBoot ELF loader?
Date: Tue, 06 Jun 2006 14:53:00 -0000 [thread overview]
Message-ID: <448596BD.30304@arcom.com> (raw)
In-Reply-To: <44857F82.1020302@brothom.nl>
Bert Thomas wrote:
>
> Example:
>
> An ELF file with 2 segments:
> segment 0: offset in file = 0, length = 0xac
> segment 1: offset in file = 0xac, length = 15
An ELF with a section having a file offset of 0 looks bogus to me. Why
would you need to load the ELF header into RAM?
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next prev parent reply other threads:[~2006-06-06 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 12:14 Bert Thomas
2006-06-06 14:53 ` David Vrabel [this message]
2006-06-06 17:23 ` Bert Thomas
2006-06-06 17:34 ` Gary Thomas
[not found] ` <4485EE86.9040909@brothom.nl>
[not found] ` <1149624902.15359.55.camel@hermes>
[not found] ` <4485F487.6080000@brothom.nl>
2006-06-06 20:49 ` Gary Thomas
2006-06-07 8:39 ` Bert Thomas
2006-06-07 11:55 ` Gary Thomas
2006-06-07 10:04 Daly, Jeffrey
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=448596BD.30304@arcom.com \
--to=dvrabel@arcom.com \
--cc=bert@brothom.nl \
--cc=ecos-devel@ecos.sourceware.org \
/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).