28.5.1. Freestanding programs

Unlike most our other assembly examples, which use the C standard library for portability, examples under freestanding/ directories don’t link to the C standard library:

As a result, those examples cannot do IO portably, and so they make raw system calls and only be run on one given OS, e.g. Linux system calls.

Such executables are called freestanding because they don’t execute the glibc initialization code, but rather start directly on our custom hand written assembly.

In order to GDB step debug those executables, you will want to use --no-continue, e.g.:

./run --arch aarch64 --userland userland/arch/aarch64/freestanding/linux/hello.S --gdb-wait
./run-gdb --arch aarch64 --no-continue --userland userland/arch/aarch64/freestanding/linux/hello.S

or in one go with tmux:

./run \
  --arch aarch64 \
  --gdb-wait \
  --tmux-args=--no-continue \
  --userland userland/arch/aarch64/freestanding/linux/hello.S \
;

You are now left on the very first instruction of our tiny executable!

This is analogous to step debugging baremetal examples.

Related:

↑ Up: Userland assembly C standard library | ⌂ Home: Linux Kernel Module Cheat | Next: nostartfiles programs →