> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:grub-devel-
> [EMAIL PROTECTED] De la part de Tomáš Ebenlendr
> Envoyé : jeudi 4 mai 2006 11:24
> À : The development of GRUB 2
> Objet : Re: RE : grub-emu state of the art
>
>
> > - let gdb kn
Eric Salomé wrote:
> Hi folks,
>
>
>
> This email to explain how I worked on grub-emu module loading, the
> choices I have made (for now) and the diff from grub-1.93 delivery.
> Marco asked me for details (well, that will make it a pretty long email
> :-)).
>
>
>
> I worked only on the i386
Tomáš Ebenlendr <[EMAIL PROTECTED]> writes:
>>> Little changes in source code, though I had to adapt asm files to
>>> passing parameters in stack (I compile without -mregparm=3 -mrtd options
>>> as I didn't want to recompile the whole C library with those passing
>>> parameters conventions).
>>
>>
>> Little changes in source code, though I had to adapt asm files to
>> passing parameters in stack (I compile without -mregparm=3 -mrtd options
>> as I didn't want to recompile the whole C library with those passing
>> parameters conventions).
>
> It would be nice to get this to work for the regul
Eric Salomé <[EMAIL PROTECTED]> writes:
> GRUB 2 Wiki
> ToDoList : Implement ModuleLoading in grub-emu
Right, and I even added this item. Sorry, I just misunderstood your
previous email.
> I worked on that : Architecture i386/pc - Emulation on Linux/Ubuntu
> grub-emu is loading all current modu
> - let gdb know about dynamically loaded modules ;-), but I guess it
> won't be the easy part.
That depends how modules are loaded in grub-emu. With standard libdl it
couldn't be problem.
But I remember a situation when we run gdb on UML(user mode linux) kernel.
When we loaded a kernel module t
