Debug Faster with GDB Dynamic Printf – No Recompile Needed

Introduction – The Pain of Traditional Debugging

When debugging, developers often toggle between sophisticated debuggers like GDB and simple log prints. Repeatedly adding, recompiling, redeploying, and later removing debug prints becomes especially painful in large projects where builds can take minutes or hours.

GDB Dynamic Printf Overview

GDB provides a Dynamic Printf (or dprintf ) feature that allows you to add formatted print statements anywhere in the program without changing the source code. The program runs normally, but when execution reaches the specified location, GDB automatically prints the defined message and continues.

Simple Example

Consider a C program test.c. Compile it with debugging symbols: gcc -g test.c -o test Start GDB and set dynamic print points at lines 6, 11, and 14:

dprintf 6, "Hello, World!
"
dprintf 11, "i = %d, a = %d, b = %d
", i, a, b
dprintf 14, "Leaving! Bye bye!
"

Running the program now prints the messages even though the binary was not recompiled.

How Dynamic Printf Works

Under the hood, a dynamic print point is a special breakpoint. Unlike ordinary breakpoints that pause execution and wait for user input, a dynamic print breakpoint executes the specified printf -style format string automatically and then resumes execution without user intervention.

Command Syntax

The syntax mirrors the C printf function, with an additional location argument that specifies where the print should fire. location can be a file name with line number, a function name, or a raw address.

dprintf location, format_string, arg1, arg2, ...

Example (same as above):

dprintf 6, "Hello, World!
"
dprintf 11, "i = %d, a = %d, b = %d
", i, a, b
dprintf 14, "Leaving! Bye bye!
"

Saving and Loading Breakpoint Information

Dynamic print points are stored as breakpoints, so they disappear when GDB exits. To persist them, use GDB’s breakpoint save/load commands.

Save breakpoints: save breakpoints file_name Load breakpoints: either start GDB with -x file_name or run source file_name inside an active GDB session.

Example workflow:

Set the dprintf points.

Verify with info break.

Save them: save breakpoints test.bp.

Later, reload with gdb -x test.bp ./test or source test.bp after starting GDB.

Conclusion

This article covered the basic usage of GDB’s dynamic printf, its underlying principle as a special breakpoint, and how to persist breakpoint configurations across debugging sessions. More advanced techniques will be explored in future updates.