Ludovic Courtès, le ven. 07 oct. 2022 00:10:15 +0200, a ecrit:
> Samuel Thibault skribis:
>
> > Ludovic Courtès, le jeu. 06 oct. 2022 15:14:13 +0200, a ecrit:
> >> such that it would stop on each trap, hopefully allowing me to see why
> >> exec is not starting.
> >
> > Also, better use exec.stati
Samuel Thibault skribis:
> Ludovic Courtès, le jeu. 06 oct. 2022 15:14:13 +0200, a ecrit:
>> such that it would stop on each trap, hopefully allowing me to see why
>> exec is not starting.
>
> Also, better use exec.static to have static addresses.
Thanks for the hint.
Of course, the thing boots
Ludovic Courtès, le jeu. 06 oct. 2022 15:14:13 +0200, a ecrit:
> such that it would stop on each trap, hopefully allowing me to see why
> exec is not starting.
Also, better use exec.static to have static addresses.
We use the dynamic version of exec "just because we can", but that makes
debugging
On Mon, Sep 26, 2022 at 09:51:32PM +0200, Samuel Thibault wrote:
> This adds acpi as bootstrap module whenever it is available. This opens the
> path for proper IRQ routing for fully-userland disk drivers.
>
> Signed-off-by: Samuel Thibault
Reviewed-by: Daniel Kiper
Daniel
Hi!
As suggested by Samuel on IRC, I did that early on in kdb:
debug traps /on
such that it would stop on each trap, hopefully allowing me to see why
exec is not starting.
--8<---cut here---start->8---
module 0: ext2fs --multiboot-command-line=${kernel-comm
