Perspectives · Debugging
GDB and OpenOCD: A Repeatable Workflow for Embedded Debugging
With a supported probe and OpenOCD, GDB can halt a target, inspect registers and memory, and show where execution went wrong.
With a supported probe and OpenOCD, GDB can halt a target, inspect registers and memory, and show where execution went wrong. Build with debug symbols and preserve the exact ELF that matches the flashed image; mismatched symbols can make source lines misleading.
Capture the call stack first, then inspect relevant registers and documented fault-status registers. Treat a damaged backtrace as evidence, not certainty. Check in a launch configuration or runbook covering target, probe, reset behavior, and connection steps. Conditional breakpoints and watchpoints can reveal who changed a value, not merely where execution stopped.