Cool stuff about GDB you didn't know
summary
GDB proves far more than break/step/print: live demos show the Python scripting API driving custom prompts and pretty-printers, the curses TUI and multi-inferior remote debugging, thread non-stop mode, and many breakpoint kinds. Hardware watchpoints are fast but limited; software watchpoints single-step and are painfully slow. Built-in process recording allows reverse execution to find a stack smash by setting a location watch and running backwards, though for larger traces the workflow moves to rr or commercial undo for usable performance.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:25Documentation
- 2:57GUI Mode
- 7:49Python
- 10:08GDB module
- 11:59Custom fonts
- 15:31Pretty Princess
- 22:22GDP init
- 24:22Remote debugging
- 28:28Watchpoints
- 32:43Catchpoints
- 33:37Multiprocess debugging
- 40:06Multiple inferiors
- 41:04Nonstop mode
- 44:41Calling inferior functions
- 46:43Time travel debugging
- 47:34Debugging time travel
- 53:53Questions
related talks
01h 02mTime Travel Debugging
17mDebuggers from scratch
01h 26mDebug C++ Code - Best Time Travel Debugging Tech
29mdrgn Writing to Memory and Breakpoints, Safely in Production?
31mTracing, Profiling & Debugging in Production (eBPF)
32mA new safe external debugger interface for CPython
24mDefeating the Transparency Feature of DBI
48mDPTrace: Dual Purpose Trace for Exploitability Analysis of Program Crashes