T

Jeremy Soller 7bfe1739fd Merge pull request #67 from Arcterus/master

Move null and zero from kernel space to user space

2017-12-18 16:25:11 -07:00

alloc_kernel

Update to new nightly API

2017-07-26 20:58:40 -06:00

linkers

Do not discard .debug section

2017-12-02 19:38:16 +00:00

src

Move null and zero from kernel space to user space

2017-12-18 14:33:06 -08:00

syscall @ 3c765737a5

Add fchown, fchmod

2017-11-28 21:48:10 -07:00

targets

Add target-c-int-width to x86_64 target

2017-10-04 18:25:59 -06:00

.gitignore

Add cargo.lock

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

.gitmodules

Make syscall a submodule

2017-08-27 10:54:11 -06:00

build.rs

Migrate from collections

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

Cargo.lock

Update Cargo.lock

2017-12-03 08:53:47 -07:00

Cargo.toml

0.1.32

2017-11-28 21:48:28 -07:00

LICENSE

Create LICENSE

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

README.md

Add documentation on using gdb

2017-12-05 01:25:54 +00: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 debug=yes

This will start a VM with and listen on port 1234 for a gdb client. Run the following to connect to it.

(gdb) target remote localhost:1234

This is great, but without debug info debugging can be quite difficult. The redox build process strips the kernel of debug info and copies the debug info to a separate file kernel.sym. You can import these symbols in gdb with the following

(gdb) symbol-file build/kernel.sym

Now you can set some interesting breakpoints and continue the process.