T

4lDO2 d7a1c6255b Fix possible race condition in paranoid ISRs.

Additionally, because it turned out to be infeasible to rely on
link-time constants in global_asm! code, I have also converted the
interrupt handlers to naked fns. This removes the proc-macro-reliant
"paste" dependency, but inserts a tiny ud2 at the end of every ISR.

2021-08-06 17:34:56 +02:00

.cargo

Update toolchain.

2021-06-17 22:42:23 +02:00

linkers

WIP: aarch64 rebase

2021-01-15 05:54:42 -07:00

res

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

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

rmm @ 37e88ff4d3

Update rmm and syscall.

2021-07-12 00:10:48 +02:00

slab_allocator @ a9e2bb08a8

Update linked_list_allocator

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

src

Fix possible race condition in paranoid ISRs.

2021-08-06 17:34:56 +02:00

syscall @ 14796acfed

Update syscall again.

2021-08-06 15:09:32 +02:00

targets

Update toolchain.

2021-06-17 22:42:23 +02:00

.gitignore

Add cargo.lock

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

.gitmodules

Update linked branch of rmm and syscall

2021-05-04 08:14:43 -06:00

ARM-AARCH64-PORT-OUTLINE.md

Update status: Toolchain spec done

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

build.rs

build.rs: aarch64: Specify target for cc::Build

2021-01-15 06:09:42 -07:00

Cargo.lock

Fix possible race condition in paranoid ISRs.

2021-08-06 17:34:56 +02:00

Cargo.toml

Fix possible race condition in paranoid ISRs.

2021-08-06 17:34:56 +02: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.