From: pei lin <telent998@gmail.com>
To: Brian Raiter <breadbox@muppetlabs.com>
Cc: Chris Evans <teknopup@gmail.com>, linux-assembly@vger.kernel.org
Subject: Re: why linux ELF base address is 0x8048000?
Date: Fri, 6 Feb 2009 13:38:54 +0800 [thread overview]
Message-ID: <d6b7c4190902052138u604bcdc7sd57916b8a3a7eff4@mail.gmail.com> (raw)
In-Reply-To: <18826.22050.739005.994893@eidolon.muppetlabs.com>
yeah,that explains some reason. But between 0x08000000 and 0x08048000
should be some other reason for X86 architecture . <<The linker and
loader>> said that "permitting most programs to use a single
second-level page table."
But i can not understand it very well.
Lin
2009/2/5 Brian Raiter <breadbox@muppetlabs.com>:
>> why linux ELF base address is 0x8048000? we can use ld to change
>> the base address or linker script.BUT why default is 0x8048000?
>> There must be some reasons or history i don't know.
>
> As far as I can tell, the reason is that this was the address used by
> SVR4, which was the first release of Unix to use ELF executables.
>
> The reason that SVR4 chose that particular address is that the stack
> top was located at 0x08000000 (growing downward, of course), and then
> the area between 0x08000000 and 0x08048000 was reserved for libc and
> possibly other system service code.
>
> b
>
prev parent reply other threads:[~2009-02-06 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 9:25 why linux ELF base address is 0x8048000? pei lin
[not found] ` <73512bc10902032321n863a27by7ac63193dfc4488a@mail.gmail.com>
2009-02-05 1:58 ` pei lin
2009-02-05 2:59 ` Brian Raiter
2009-02-06 5:38 ` pei lin [this message]
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=d6b7c4190902052138u604bcdc7sd57916b8a3a7eff4@mail.gmail.com \
--to=telent998@gmail.com \
--cc=breadbox@muppetlabs.com \
--cc=linux-assembly@vger.kernel.org \
--cc=teknopup@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).