bea674764359d6e523d7db5ca21697f97107d33f
Currently, there are some things that need to be set up by userspace that the kernel previously did. These include telling firmware when the I/O APIC is used, and most importantly, shutting down the system. The former is not particularly important, but for the latter I think that we could implement this using a "shutdown pipe". Essentially it will be a file that triggers an event shutting down, which would be used to notify to acpid that the kernel is requesting a shutdown.
kernel
Redox OS Microkernel
Debugging the redox kernel
Running qemu with the -s flag will set up qemu to listen on port 1234 for
a gdb client to connect to it. To debug the redox kernel run.
make qemu gdb=yes
This will start a VM with and listen on port 1234 for a gdb or lldb client.
gdb
If you are going to use gdb, run the following to load debug symbols and connect to your running kernel.
(gdb) symbol-file build/kernel.sym
(gdb) target remote localhost:1234
lldb
If you are going to use lldb, run the following to start debugging.
(lldb) target create -s build/kernel.sym build/kernel
(lldb) gdb-remote localhost:1234
Debugging
After connecting to your kernel you can set some interesting breakpoints and continue
the process. See your debuggers man page for more information on useful commands to run.
Description
RedBear Operating System, based on RedoxOS. Licenced under MIT license.
https://redbearos.org
Languages
Rust
98.8%
Assembly
0.6%
Linker Script
0.5%
Makefile
0.1%