public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Bert Thomas <bert@brothom.nl>
Cc: David Vrabel <dvrabel@arcom.com>, ecos-devel@ecos.sourceware.org
Subject: Re: bug in RedBoot ELF loader?
Date: Tue, 06 Jun 2006 17:34:00 -0000	[thread overview]
Message-ID: <1149615229.15359.41.camel@hermes> (raw)
In-Reply-To: <4485C3FA.30201@brothom.nl>

On Tue, 2006-06-06 at 19:05 +0100, Bert Thomas wrote:
> David Vrabel wrote:
> > 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?
> 
> Example: readelf -a /bin/ls
> 
> <deletia>
> Program Headers:
>    Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
>    PHDR           0x000034 0x08048034 0x08048034 0x000e0 0x000e0 R E 0x4
>    INTERP         0x000114 0x08048114 0x08048114 0x00013 0x00013 R   0x1
>        [Requesting program interpreter: /lib/ld-linux.so.2]
>    LOAD           0x000000 0x08048000 0x08048000 0x0e994 0x0e994 R E 0x1000
>    LOAD           0x00f000 0x08057000 0x08057000 0x003c0 0x0074c RW  0x1000
>    DYNAMIC        0x00f188 0x08057188 0x08057188 0x000d0 0x000d0 RW  0x4
>    NOTE           0x000128 0x08048128 0x08048128 0x00020 0x00020 R   0x4
>    GNU_EH_FRAME   0x00e968 0x08056968 0x08056968 0x0002c 0x0002c R   0x4
> <deletia>
> 
> Read:
> http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
> 
> "(it's normal behavior for a program to include its ELF header and 
> program header table in its memory image)"

Bunk :-(  Shades of old COFF files...

> 
> I'd aggree with you however...
> 
> Bert
-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2006-06-06 17:34 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
2006-06-06 17:23   ` Bert Thomas
2006-06-06 17:34     ` Gary Thomas [this message]
     [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=1149615229.15359.41.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=bert@brothom.nl \
    --cc=dvrabel@arcom.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).