Verified Commit 126e0859 authored by jD91mZM2's avatar jD91mZM2


parent 1c7057b2
Pipeline #8112 passed with stage
in 29 seconds
title = "Public Announcement: You Can Now Debug Programs Using GDB on Redox OS"
author = "jD91mZM2"
date = "2020-07-27T11:52:09+02:00"
<img class="img-responsive" src="/img/screenshot/gdb-complete.png" alt="Debugging with GDB, improved" />
# Introduction
If you've been following my [Redox Summer of Code progress](/news/rsoc-gdb-0/),
you might have noticed a long break after the [last post](/news/rsoc-gdb-1/). At
first, the reason was that I just lost track of time. My previous years of RSoC
have followed a similar inconsistent schedule, which I now refer to as an
interval of one blog post per "programmer week", where a "programmer week" is
anywhere from 3 days to a month...
Now, the reason for not finishing is that I'm basically done! That's right, GDB
has served us reliably for the past few weeks, where we've been able to debug
our dynamic linker (``) and find problems with shared libraries. We got to
the point where the amazing [@bjorn3]( has managed to
run his first rust program compiled on Redox using his [rustc cranelift
While obviously we would've found the bugs without gdb eventually, I'd love to
attribute enough credit to it that it warrants being posted here!
<img class="img-responsive" src="/img/screenshot/rustc-cranelift.png" alt="Hello, World!" />
# Usage
The easiest way to use gdb on Redox, is to uncomment `gdbserver` and
`gnu-binutils` from your `filesystem.toml`, and run `gdb-redox <absolute
filepath> [args...]`. It will launch our custom `gdbserver` and connect to it
from gdb over <abbr title="Inter-Process Communication">IPC</abbr>. The
"disadvantage" of this is that you're forced to copy your source code over to
Redox if you want pretty symbols and file numbers.
You can also choose to start the standalone `gdbserver <absolute filepath>
[args...]`, which will open a socket you can connect to from GDB. This allows
you to connect from a host Linux system using your favorite tools like normal,
by first running `(gdb) target remote :64126` to connect to the running server.
This approach forces you to forward `:64126` over the network, which can be done
by starting Redox with the `net=redir` flag.
# Troubleshooting
If you're having trouble getting Redox working, join me in our developer chat by
sending an email to []( and asking for
an invite link.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment