There are numerous areas in the kernel where a heap allocation failure is being silently ignored, merely asserted against or otherwise mishandled. Assertions may suffice for allocations on initialization (where system bringup would otherwise be impossible), but allocation failures which may reasonably happen during runtime must be addressed.

See, for example, #1199; all the various calls to the

display_bsod internally calls the map_framebuffer syscall to map the framebuffer, because we . were lazy and didn't want to duplicate code. However this syscall retrieves the current process to map it in its process memory.

When we're panicking during early boot, CURRENT_PROCESS is None and this panics in the panic handler.

We should instead do a second function that maps it in the k

Check out kernel/kernel/kshell.c and kernel/libk/string.c... Replace the 'local' string algorithms in kshell with string.c ones. Also check if string.c/string.h implements all the the standard string functions