Time Travel Debugging
summary
Tool demos a concrete claim: the WinDbg preview on Windows 10 records every instruction into a trace file that the debugger then replay[s] forward and backward and treats as a queryable database. No rebuild or special linking is required; multithreaded execution and shared‑memory I/O are preserved (no serialization). Live examples find a buffer overrun from passing byte size instead of element count, a lost GetLastError overwritten by a later API call, and a vector swap exposing a use‑after‑free via small‑string optimization by querying memory accesses and allocation/free patterns.
AI-written summary · about
chapters (7)
- 0:00Introduction to TTD
- 1:13How time travel works
- 8:12Basic usage demonstration
- 14:45Debugging a crash
- 24:22Advanced querying concepts
- 27:30Using queries for complex bugs
- 44:54Analyzing a complex memory bug
related talks
25mTime Travel Debuggers
15mGive me 15 minutes & I'll change your view of GDB
26mTime travel debugging: A step-by-step guide
37mTime Travel Debugging JavaScript Applications
01h 01mBeyond step-by step debugging in Visual Studio
37mThe Bright Future of Debuggers: Challenges and Opportunities
01h 01mBack to Basics: Debugging in Cpp
59m“GDB - A Lot More Than You Knew"