The Bright Future of Debuggers: Challenges and Opportunities
summary
Claims that debugging consumes ~50% of dev time costing $312B motivate concrete tools: a formal Multiverse debugging shows all interleavings for nondeterministic actors and provides queries to prune state (but faces state explosion); a hybrid out-of-place debugging runs parts of firmware on the host to avoid slow remote stepping and supports back-in-time replay for WASM in a Visual Studio plugin; a block-based YouTube-style time travel for Scratch records and replays events and proves usable with children.
AI-written summary · about
chapters (8)
- 0:00Debugging is fun
- 3:47Debuggers in practice
- 9:54Next-gen debugging techniques
- 10:14Multiverse debugging
- 15:40Debugging resource-constrained devices
- 19:57Debugging Scratch
- 22:46Debugging future directions
- 24:56Q&A
related talks
51mProgramming is Debugging
38mFrom the Exorcist to Hercule Poirot
21mAbstract Debuggers: Exploring Program Behaviors Using Static Analysis Results
58mDebugging #Java
31mThe Science and Magic of Debugging
53mDebugging: past, present and future
20mDebugging: Techniques for Uncertain Times
01h 02mTime Travel Debugging