Upravit

Sdílet prostřednictvím

Time Travel Debugging - Record a trace

  • Článek

Time travel debugging logo featuring a clock.

This section describes how to record time travel debugging (TTD) traces. There are two ways to record a Trace in WinDbg, Launch Executable (advanced) and Attach to a process.

Launch executable (advanced)

To launch an executable and record a TTD trace, follow these steps.

  1. In WinDbg, select File > Start debugging > Launch executable (advanced).

  2. Enter the path to the user mode executable that you wish to record or select Browse to navigate to the executable. For information about working with the Launch Executable menu in WinDbg, see WinDbg - Start a user-mode session.

  3. Check the Record with Time Travel Debugging box to record a trace when the executable is launched.

    Screenshot of WinDbg with start recording checkbox in the Launch Executable (advanced) screen.

  4. If you select Configure and Record you will be able to configure a location for the trace file.

    Screenshot of Configure Recording dialog with Browse button and file path displayed.

  5. To limit recording to specific modules, check "Record subset of execution" and type in the module names. For example, if you only want to record the execution of notepad.exe, type "notepad.exe" in the text box. If you want to record the execution of notepad.exe and kernelbase.dll, type "notepad.exe,kernelbase.dll" in the text box.

    Screenshot of Configure Recording dialog with record subset of execution checked and module list text box.

  6. Select OK to launch the executable and start recording.

  7. The recording dialog appears indicating the trace is being recorded.

    Screenshot of TTD recording popup with Stop and Debug, and Cancel buttons.

  8. See How to record for information on recording.

Attach to a process

To attach to a process and record a TTD trace, follow these steps.

  1. In WinDbg, select File > Start debugging > Attach to process.

  2. Select the user mode process that you wish to trace. For information about working with Attach to a process menu in WinDbg, see WinDbg - Start a user-mode session.

    Screenshot of WinDbg displaying start recording checkbox in Attach to Process screen.

  3. Check the Record Process with Time Travel Debugging box to create a trace when the executable is launched.

  4. Select Attach to start recording.

  5. The recording dialog appears indicating the trace is being recorded.

    Screenshot of TTD recording popup with Stop and Debug, and Cancel options.

  6. See How to record for information on recording.

How to record

  1. The process is being recorded, so this is where you need to cause the issue that you wish to debug. You may open a problematic file or select a specific button in the app to cause the event of interest to occur.

  2. While the recording dialog box is being displayed you can:

    • Stop and debug - Choosing this will stop the recording, create the trace file and open the trace file so you can start debugging.
    • Cancel - Choosing this will stop the recording and create the trace file. You can open the trace file at a later time.

  3. Once your recording is complete, close your app or hit Stop and debug.

    Note

    Both Stop and debug and Cancel will terminate the associated process.

  4. When the application being recorded terminates, the trace file will be closed and written out to disk. This is the case if your program crashes as well.

  5. When a trace file is opened, the debugger will automatically index the trace file. Indexing allows for more accurate and faster memory value look ups. This indexing process will take longer for larger trace files.

    ...
00007ffc`61f789d4 c3              ret
0:000> !index
Indexed 1/1 keyframes
Successfully created the index in 96ms.

    Note

    A keyframe is a location in a trace used for indexing. Keyframes are generated automatically. Larger traces will contain more keyframes. When the trace is indexed, the number of keyframes is displayed.

  6. At this point you are at the beginning of the trace file and are ready to travel forward and backward in time.

    Tip

    Using breakpoints is a common approach to pause code execution at some event of interest. Unique to TTD, you can set a breakpoint and travel back in time until that breakpoint is hit after the trace has been recorded. The ability to examine the process state after an issue has happened, to determine the best location for a breakpoint, enables additional debugging workflows. For an example of using a breakpoint in the past, see Time Travel Debugging - Sample App Walkthrough.

Next Steps

Now that you have a recorded a TTD trace, you can replay the trace back or work with the trace file, for example sharing it with a co-worker. For more information, see these topics.

Time Travel Debugging - Replay a trace

Time Travel Debugging - Working with trace files

Time Travel Debugging - Troubleshooting

Time Travel Debugging - Sample App Walkthrough

See Also

Time Travel Debugging - Overview