jD91mZM2 fe705d9b63 Switch to 2018 edition
Most of this was generated by the absolutely extraordinary `cargo fix`
subcommand. There were still 2 errors and a few warnings to patch up,
but compared to the normal 600+ errors, I'd say the fixer did a damn
good job! I'm also amazed that I could still start the VM after this,
I half expected some kinds of runtime failure...
2019-06-21 12:12:01 +02:00
2018-01-10 19:27:05 -07:00
2019-06-21 12:12:01 +02:00
2018-11-08 17:11:06 -07:00
2018-06-12 12:30:44 -06:00
2019-04-13 21:57:58 -06:00
2019-06-21 12:12:01 +02:00
2017-09-26 12:57:43 -06:00
2018-01-10 21:31:28 +00:00
2017-10-28 02:42:08 +02:00

kernel

Redox OS Microkernel

MIT licensed docs

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
No description provided
Readme 2.6 MiB
Languages
Rust 97%
Assembly 2.9%
C 0.1%