What Really Happens When You Hit a Breakpoint • Sy Brand • GOTO 2025

What Really Happens When You Hit a Breakpoint • Sy Brand • GOTO 2025

by Sy Brand

Formal & Physical Sciences Computing & Cybersecurity UMComputer programmingUMAProgramming techniques
🎙 Sy Brand 👥 1.1M 📅 March 18, 2026 ⏱ 41 min 👁 9K 📄 expert opinion 🧭 2026-08-02
Available in: English (current) Français

Keywords

debuggerbreakpointptraceDWARFx86

Summary

In this GOTO Copenhagen 2025 talk, Sy Brand, author of ‘Building a Debugger’, demystifies the internal workings of native code debuggers. He outlines the architecture involving the debugger, the target process, the binary with debug information, and the operating system. He explains how debuggers manipulate memory and registers using system calls like ptrace on Linux. The core focus is on breakpoints: how debug information (DWARF) maps source lines to machine instructions, and how software breakpoints work by replacing an instruction byte with an INT3 trap, then restoring and single-stepping to continue. He also covers hardware breakpoints and watchpoints, which use special registers to break on memory access. Stepping mechanisms (step over, step into, step out) are explained, along with stack unwinding to get call stacks. The talk concludes with techniques for reading variables and calling functions in the debugged process, emphasizing the role of debug information and ABI conventions.

149 words

Critical Evaluation

The talk provides a comprehensive and technically accurate overview of debugger internals, suitable for developers with some systems programming background. Sy Brand’s expertise is evident, and the explanations are clear, using concrete examples and diagrams. The content is well-structured, progressing logically from basic concepts to more advanced topics. The use of ptrace and DWARF is correctly described, and the explanation of software breakpoints is particularly insightful. The talk does not shy away from complexities, such as the quirks of the ptrace API and the intricacies of DWARF line tables. The argumentation is solid, and the information is reliable, though it is based on the speaker’s experience and not peer-reviewed. The talk is an excellent resource for understanding debugger internals, and it aligns well with the title. The only minor criticism is that some topics are covered briefly due to time constraints, but the speaker appropriately points to his book for deeper dives. Overall, this is a high-quality technical presentation.

159 words

Title / Content Match

The title accurately reflects the content, which focuses on the internal workings of breakpoints and other debugger features.

Quality & Reliability

9/10

Presentation by an expert author of a book on debuggers, with detailed technical explanations grounded in system-level mechanisms. The content is accurate and well-structured, though it is a conference talk and not peer-reviewed.

Chapters

Cited Sources

Concurring Sources

External References

Contribution & Novelties

The talk provides a clear, practical explanation of debugger internals, focusing on Linux and x86. It demystifies breakpoints, watchpoints, and stepping, and explains how debug information is used. The speaker’s expertise adds credibility, and the talk serves as an excellent introduction to systems programming concepts.

Pour aller plus loin :

  • DWARF Debugging Standard — Official specification for debug information format.
  • ptrace(2) man page — Detailed documentation of the ptrace system call.
  • Intel 64 and IA-32 Architectures Software Developer’s Manual — Reference for x86 instruction set and debug registers.

88 words

Radar Profile

The radar profile shows high scores across all dimensions, indicating a well-rounded and reliable technical talk. The strong performance in information quality and reliability reflects the speaker's expertise and the accurate technical content.

Reliability 9/10