Pro lesson · Preview

Debugging with GDB

Pause, inspect, and step through a running program: GDB's core commands (break/continue/step, print, backtrace), connecting to an embedded target over a gdbserver, and the optimization gotcha.

24 min read

This lesson is part of Pro

Upgrade to unlock the full lesson and the complete interview Q&A.

Unlock with Pro

5 interview questions on this topic

Each one opens a full worked answer.

What can GDB do that printf debugging can't?How does GDB connect to and debug an embedded target?Why is debugging optimized code harder, and how do you handle it?What's the difference between next and step in GDB?What is a Heisenbug in the context of using a debugger, and when does it matter?

This is just the start

Sign up free to track your progress through this course, mark lessons complete, and work through the full interview Q&A.

Sign up freeSee pricing

More in Debugging & Toolchain

The ToolchainThe Build Process & MakefilesLinker Scripts & Memory Sections
On-Chip Debugging: JTAG & SWD
Breakpoints & Watchpoints
Logic Analyzer & Oscilloscope
Debugging with GDB | EmbeddedPrep.io