Re: Problem using .zerofill / -segaddr to create very large segments
Re: Problem using .zerofill / -segaddr to create very large segments
- Subject: Re: Problem using .zerofill / -segaddr to create very large segments
- From: Nat! <email@hidden>
- Date: Wed, 23 Sep 2009 00:29:01 +0200
Am 21.09.2009 um 23:57 schrieb Brian Mastenbrook:
The problem is that code, the malloc heap, etc. are already placed
in memory at that point. Using a zero-fill segment in an object
reserves the heap space first, which forces the linker to move any
relocatable code and the malloc heap to be allocated elsewhere. This
is useful in general for image-based programming languages that are
natively compiled, as you can save an image and then re-map it in
memory as it was originally represented.
Maybe it's possible to setup a multiple stage-boot system. The basic
app is very small basically just allocates the region with mmap, no
linkage to the C runtime and then loads the rest as a bundle ?
Ciao
Nat!
------------------------------------------------------
Hence, if the present world doth go astray,
In you the cause is, be it sought in you;
And I therein will now be thy true spy. - Alighieri
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden