a7da393cf569416314fd1c9e016cece352537929
Signals now cause an event, and there's a way to continue until the next signal. I can see this being used for detection of `int3` although I'm not entirely sure as it may prove being too late to stop abortion of process.
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 debug=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
C
37.5%
C++
37.2%
JavaScript
6.7%
QML
3.4%
HTML
3.2%
Other
11.4%