|
From: Nicholas N. <nj...@ca...> - 2004-07-15 12:55:44
|
On Wed, 14 Jul 2004, Nicholas Nethercote wrote: >> Looks reasonable to me. It would be really nice to fix the constant >> address for info.map_base in stage1. Hm, with this arrangement, info. >> mapbase for stage2 is essentially where the brk used to be - after the >> main executable. Stage1 can work out where it is just by looking at >> stage2's ELF mappings. > > How do you do that? Do the mappings say how big the executable is? What > about stage2's stack? It has one, it's small, but system malloc() is called > a few times at startup. s/stack/heap I see the info->exe_end is set in ume.c, ume.h describes it as the "highest (allowed) address", but what does this actually mean? What about space for stage2's data? N |