StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy do virtual memory addresses for linux binaries start at 0x8048000?
primarykey
Id
2966426
data
AcceptedAnswerId
2966486
AnswerCount
1
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-06-03T13:35:03.723
FavoriteCount
13
LastActivityDate
2010-06-03T13:40:54.830
LastEditDate
LastEditorUserId
0
OwnerUserId
2533756
ParentId
0
PostTypeId
1
Score
30
ViewCount
3498
LastEditorDisplayName
text
Body
Disassembling an ELF binary on a Ubuntu x86 system I couldn't help but notice that the code(.text) section starts from the virtual address 0x8048000 and all lower memory addresses seem to be unused. This seems to be rather wasteful and all Google turns up is either <a href="http://linux.derkeiler.com/Newsgroups/comp.os.linux.development.system/2006-02/msg00090.html" rel="noreferrer">folklore involving STACK_TOP</a> or protection against null-pointer dereferences. The latter case looks like it can be fixed by using a single page instead of leaving a 128MB gap. So my question is this - is there a definitive answer to why the layout has been fixed to these values or is it just an arbitrary choice?
Tags
<linux><x86><elf><memory-layout>
Title
Why do virtual memory addresses for linux binaries start at 0x8048000?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USaks
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhy do virtual memory addresses for linux binaries start at 0x8048000?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhy do virtual memory addresses for linux binaries start at 0x8048000?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhy do virtual memory addresses for linux binaries start at 0x8048000?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI don't know the actual answer; but perhaps this article might either help or at least provide an interesting read! http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
 singulars
 PostPostId
 POWhy do virtual memory addresses for linux binaries start at 0x8048000?
 UserUserId
 USRuss Clarke

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.