T

Wren Turkal 03e60f7da6 Add log crate and add a generic logger.

This is the first step of integrating the log crate as the main way to
log messages from the kernel.

Also, reexport all log macros. This module should eventually be the
only logging API used in the kernel.

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

2020-08-08 20:48:41 -07:00

.cargo

Use cargo for lto over manually entering rustflags

2020-08-01 13:19:12 +02:00

linkers

Remove comment from linker file

2018-01-10 19:27:05 -07:00

res

Add support for graphical debug, to be used during ACPI phase

2018-03-11 11:36:58 -06:00

slab_allocator @ a9e2bb08a8

Update linked_list_allocator

2018-04-28 21:45:19 -06:00

src

Add log crate and add a generic logger.

2020-08-08 20:48:41 -07:00

syscall @ a7d066a3a2

Update redox_syscall again

2020-08-03 16:08:15 +02:00

targets

Update for new rust

2018-11-08 17:11:06 -07:00

.gitignore

Add cargo.lock

2017-07-26 07:44:24 -06:00

.gitmodules

Update links to gitlab

2018-06-12 12:30:44 -06:00

ARM-AARCH64-PORT-OUTLINE.md

Update status: Toolchain spec done

2018-04-16 02:53:59 +05:30

build.rs

Include trampoline in kernel to fix multi_core on EFI

2020-07-15 21:46:15 -06:00

Cargo.lock

Add log crate and add a generic logger.

2020-08-08 20:48:41 -07:00

Cargo.toml

Add log crate and add a generic logger.

2020-08-08 20:48:41 -07:00

clippy.sh

Add more clippy lints

2019-10-06 11:15:01 -06:00

LICENSE

Create LICENSE

2017-09-26 12:57:43 -06:00

README.md

Update README's debugging instructions

2020-01-25 20:03:57 -05:00

Xargo.toml

Migrate from collections

2017-10-28 02:42:08 +02:00

README.md

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.