Multicore Debugging with GDB
summary
GDB adds non-stop mode (leave some threads running) and experimental PTC/IT sets to operate on groups of processes/threads/cores so one command can continue or step many targets at once; set implementation exists on a branch but isn’t finished. Target-side agents and a bytecode engine move breakpoint/condition evaluation onto the target — target-side breakpoints — reducing host bottlenecks; condition evaluation shipped in GDB 7.5. Prototypes include a statically linked debug thread that worked for a customer and a GDB server agent model; a high-performance single-packet protocol is proposed but not implemented.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:56GDB, the GNU Debugger
- 7:49Target System Trends
- 9:21Approaches
- 11:40Threads Run Simultaneously
- 12:59Non-stop Debugging
- 14:22Displaced Stepping
- 15:37Extending the User Interface
- 17:51Set Examples
- 20:13Commands Using Sets
- 22:24Set History
- 26:01The Host as Bottleneck
- 27:52Target-side Operations
- 31:17Target-side Breakpoint Conditions
- 33:04Towards a New Remote Protocol
- 34:41Multicore Services Framework
- 36:55GDB in the Services Framework
- 38:41Artist's Conception
related talks
01h 29mMore GDB wizardry and 8 other essential Linux application debugging tools
01h 10mCool New Stuff in GDB 9, 10 and 11
18mFavourite GDB developers tricks
32mCross Debugging on Linux : A History, Current State of the Art and Coming Improvements
25mDebugging memory issues with Valgrind and GDB
38mProgrammable debuggers and the Linux kernel (drg...
01h 29mModern Linux C++ Debugging Tools - Under the Covers
58m“Debugging Linux C++”