Snippets Groups Projects

"git@gitlab.redox-os.org:redox-os/kernel.git" did not exist on "dafd2e9f98e02cb1796dfda55cbf312bc30c6012"

Add a way to customize how logging is done.

Wren Turkal authored 4 years ago

Each architecture may have a different method to enable logging. Now
that can be customized with a function passed to the init_logger
function.

Also, provide a minimal x86_64 implementation.

This is the first commit where you can see logging coming from the log
crate.

Signed-off-by: Wren Turkal <wt@penguintechs.org>

dafd2e9f

dafd2e9f 4 years ago

Name	Last commit	Last update
.cargo
linkers
res
src
targets
slab_allocator @ a9e2bb08
syscall @ a7d066a3
.gitignore
.gitmodules
ARM-AARCH64-PORT-OUTLINE.md
Cargo.lock
Cargo.toml
LICENSE
README.md
Xargo.toml
build.rs
clippy.sh

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.