An Experience of Time Travel Debugging
Tert-Butyllithium

Introduction to Windbg: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/time-travel-debugging-overview
Video Demo: https://www.youtube.com/watch?v=l1YJTg_A914

An Example

Requirement:

  • Compile by MSVC (no need to set compile target to DEBUG)
    Since windows executions are certainly compiled by MSVC, WinDBG is a general platform for Time Travel Debugging

windbg.png

In my imagination:

  1. its record relays on capturing after every signle instrction
  2. “debug” only supports browser instead of run, so it is essentially a snapshot browser

Overhead

I have writen a huge cycle, and found a 200%? of run time, accomplished 4.67 GB trace file by 3.6 billion instructions.