“Time Travel Debugging..."
summary
A Windows reverse debugger that captures a record/replay trace of a process and lets WinDbg replay it forwards and backwards, query it (DX / LINQ-style) and jump to events; demos show finding a stack-corrupting buffer overflow by stepping back to the return, and locating who wrote a bad pointer with memory breakpoints (BA). Recorder runs on multiple cores (multicore recording), supports shared memory and sync IO, produces traces (Notepad ~200 MB), needs admin to record, has noticeable record overhead but much faster, queryable replay.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:04What is Time Travel Debugging
- 7:04Recording and replaying a trace
- 12:44Debugging a crash with TTD
- 23:16Debugging Chakra engine with TTD
- 33:18Querying traces for debugging
- 35:27Solving a media player bug with queries
- 45:40Future plans for TTD
- 47:05Answering saved audience questions
- 51:04Scripting the debugger with JavaScript
- 51:25Q&A session begins
related talks
58mTime Travel Debugging - Debug Complex C++ Bugs With Software from Undo
53mDebugging .NET Apps
01h 00mBuilding your own profiling and diagnosis tools with Event Tracing for Windows
55mPower your .NET application with the new generation of diagnostics
58mETW - Monitor Anything, Anytime, Anywhere
52mApplication-Level Debugging and Profiling: Gaps in the Tool Ecosystem
09mSession Replay
31mDebugging Techniques in Elixir