On Tue, Apr 06, 2004 at 09:44:35AM +0200 or thereabouts, Yoshinori K. Okuji wrote: > On Tuesday 06 April 2004 06:57, Joshua Oreman wrote: > > Is there any way, when in a Multiboot kernel, to determine the load > > address and length of the loaded kernel code? The Multiboot spec says > > the former is "anywhere the loader sees fit", and the latter is > > obviously kernel-specific. > > Where is "anywhere the loader sees fit" in the spec? Multiboot-compliant > boot loaders must load a kernel at the location the kernel specifies in > its Multiboot header.
Thanks for the info; I distinctly remembered seeing that phrase in the spec. Never mind. > > > I have a feeling this may be possible via > > the ELF symbol table (using _start) but I don't know the ELF format > > well enough to get from the section header (which is provided) to the > > symbol table. Is there an easier way? I'm looking to make sure that > > memory is not allocated from the middle of the kernel. > > _start is the easiest. For now I'm using sum of all (PROGBITS | NOBITS) sections. Is there a way to *get* to the symbols from the section header? -- Josh _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
