Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • unlink-path-format
  • scheme-fmt
  • riscv64
  • 0.6.0
  • 0.1.54
  • 0.5.0
  • 0.3.5
8 results
Compare
jD91mZM2's avatar
Remove deadlock-prone mutex in proc.rs
jD91mZM2 authored 
I believe this could cause a deadlock if a blocking I/O operation was
interrupted by a signal or otherwise, and decided to exit and close
all files. It's unlikely to happen, but it can happen nontheless. This
removes the mutex, but it's difficult to keep the code tidy. Hopefully
this is good enough.
ab1a12ad
History
jD91mZM2's avatar ab1a12ad
History
Name Last commit Last update
linkers
res
src
targets
slab_allocator @ a9e2bb08
syscall @ 6ba71e7e
.gitignore
.gitmodules
ARM-AARCH64-PORT-OUTLINE.md
Cargo.lock
Cargo.toml
LICENSE
README.md
Xargo.toml
build.rs
clippy.sh
README.md

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.