From: "Daly, Jeffrey" <jeffrey.daly@intel.com>
To: "eCos development" <ecos-devel@ecos.sourceware.org>
Subject: RE: bug in RedBoot ELF loader?
Date: Wed, 07 Jun 2006 10:04:00 -0000 [thread overview]
Message-ID: <7905FFCA2E893B41B7697977B01334D46A3EB7@hdsmsx411.amr.corp.intel.com> (raw)
Uh, are you confusing the difference between the disk image of a program
(which has the headers) and the the memory image of the program (which
only includes the instructions/data)?
-----Original Message-----
From: ecos-devel-owner@ecos.sourceware.org
[mailto:ecos-devel-owner@ecos.sourceware.org] On Behalf Of Bert Thomas
Sent: Wednesday, June 07, 2006 5:38 AM
To: Gary Thomas
Cc: eCos development
Subject: Re: bug in RedBoot ELF loader?
> Of course - the headers are just that; descriptions of stuff to come
> _later_ in the file. A sane ELF file (files created by GNU ld behave
> this way) will have the various section headers first, followed by
> the actual program segments. There is no need for a loader (like
> RedBoot which is what started this discussion) to ever load the
> headers as part of the image, rather only process them to figure
> out what needs to be loaded and where. For example, a RAM program
I aggree with you on the sanity part. However, I bet that most if not
all Linux executables have a segment that include the headers. I assume
you are working on a Linux machine. Could you try readelf on ls for
example?
Again, it is not that I disaggree with you. It is just that I observe it
isn't the way you and I expected it to be.
I suspect the reason that your example doesn't have a segment that
includes the headers has something to do with the linker script you
wrote to link that program.
Bert
next reply other threads:[~2006-06-07 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 10:04 Daly, Jeffrey [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 12:14 Bert Thomas
2006-06-06 14:53 ` David Vrabel
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
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=7905FFCA2E893B41B7697977B01334D46A3EB7@hdsmsx411.amr.corp.intel.com \
--to=jeffrey.daly@intel.com \
--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).