Fix your hardest bugs with ease with Time Travel Debugging - Session Interview With Greg Law
summary
Claims a record-and-replay engine that records real runs and lets users rewind to any executed line and inspect variables, memory and registers, not a GDB extension but exposing GDB via udb. Works with optimized production builds and terabyte working sets that run for days, scales comfortably to ~16–32 threads (degrades with hundreds+ threads), and demos live console debugging and implementation tradeoffs rather than a sales pitch.
AI-written summary · about
chapters (8)
- 0:00Interview intro
- 0:46Greg Law's GDB journey
- 1:50Undo's time travel debugging
- 3:57Time travel in production
- 6:26Debug builds and scalability
- 7:27Multithreaded bugs are hard
- 8:30Upcoming talk focus
- 9:34Why conferences matter
related talks
37mThe Bright Future of Debuggers: Challenges and Opportunities
21mAbstract Debuggers: Exploring Program Behaviors Using Static Analysis Results
30mA Series of Unfortunate Bugs
14mShow Me Why It's Correct: Saving 1/3 of Debugging Time in Program Repair with(…)
40mLessons from two decades of writing bad code
27mDebugging product engineering organizations
26mThe evolution of a flight recorder
03mDebuggability