Since my joke about the Venus Sucker Shrubs failed to resonate with Oryan, I decided to assist him with the software anomaly instead.

Considering I originate from a binary star system, I was apparently the closest thing available to a binary expert.

Oryan suggested I begin by learning how to inspect binaries using a utility called gdb.

Apparently humans enjoy naming debugging tools after insects as well.

If you ask me, a Venus Sucker Shrub would probably still be more useful.

INTRODUCTION

Maintenance Note: Programs, like gardens, are often healthiest when observed carefully rather than uprooted immediately. Debuggers allow us to examine a system while it is still alive.

The GNU Debugger (gdb) is a command-line utility that is useful for analyzing a binary executable during runtime. It allows you to track down segmentation faults in Goldie's internal processing and to examine compiled programs whose source code has long since scattered like dandelion seeds on a solar wind.

1. PREPARING THE BINARY

If your program is infested with bugs that are not of the insect variety, compiling with debug symbols allows you to trace their migration patterns. This is accomplished using the -g flag.

gcc -g -o saraphile saraphile.c

2. LAUNCHING GDB

Commence debugging by passing a compiled executable as an argument. Be careful to avoid arguments with AIME while debugging. Unexpected behavior is difficult to distinguish from expected behavior.

gdb ./saraphile

Once initiated, you will see the (gdb) interactive prompt. You can exit at any time by typing quit or q.

3. SETTING BREAKPOINTS

Setting breakpoints before execution will stop your program at a specified location so you can analyze its state at that given moment, but it won't stop Goldie K9000 from breaking the robot vacuum cleaner (again).

• break main (or b main) – Stops execution at the entry point of the main function.
• break 42 – Ceases execution at line 42 of the current source file.
• break *0x7FFE5367E044 – Pauses execution at a specific raw memory address.
• info break – Lists all breakpoints and their index number.
• delete 1 (or d 1) – Deletes a breakpoint at index 1.

4. RUNNING AND STEPPING THROUGH CODE

• run (or r) – Starts the program from the beginning.
• run arg1 arg2 – Starts the program while passing command-line arguments.
• next (or n) – Executes the next line of code, stepping over function calls.
• step (or s) – Executes the next line of code, stepping into function calls.
• continue (or c) – Resumes normal execution until the next breakpoint or crash. Much like allowing a vine to grow unchecked to see where it becomes a problem.
• finish – Executes the remainder of the current function and pauses upon return.

5. INSPECTING VARIABLES AND MEMORY

When the program reaches a breakpoint and stops, use these commands to inspect the program's internal state and determine which roots lead to the problem.

• print var (or p var) – Displays the current value of a variable.
• watch var – Sets a watchpoint that pauses execution whenever the value of var changes.
• backtrace (or bt) – Prints the function call stack to show exactly how your program reached this execution point.
• info locals – Lists all local variable values in the current stack frame.

6. ASSEMBLY DEBUGGING WITHOUT SOURCE CODE

If you do not have the source code, you must interact directly with registers and CPU instructions:

• layout asm – Switches GDB to a split-screen Text User Interface (TUI) showing live assembly instructions at the top.
• disassemble main (or disas main) – Dumps the raw assembly instructions for the specified function.
• info registers (or i r) – Shows the current values stored inside the CPU registers (e.g., EAX, RSP, RIP).
• stepi (or si) – Steps forward by exactly one machine instruction.
• nexti (or ni) – Steps over a machine instruction (such as a CALL instruction).
• x/gx $rsp – Examines memory content. This specific command inspects one giant word (64-bits) in hexadecimal format at the stack pointer address.

IN CONCLUSION

GNU Debugger (gdb) is a useful tool for locating and eliminating software bugs. For all other varieties, I recommend Venus Sucker Shrubs. They are remarkably effective and significantly less judgmental than AIME.

You can learn more about gdb by checking the manual pages on your system.