Add instructions on how to capture TDD traces (#9807)
Blue committed
Aug 15, 2023 at 18:37 UTC
aca8f663e8b6b8982b582fbe37db02a50eef916a
1 file changed
+29
-1
CONTRIBUTING.md
+29
-1
@@ -221,4 +221,32 @@ Once you're done, crash dump collection can be disabled by running the following
221
222
```
223
reg.exe delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /f
224
-```
\ No newline at end of file
224
+```
225
+
226
+### 12) Collect wslservice time travel debugging traces
227
+
228
+To collect time travel debugging traces:
229
+
230
+1) [Install Windbg preview](https://apps.microsoft.com/store/detail/windbg-preview/9PGJGD53TN86?hl=en-us&gl=us&rtc=1)
231
+
232
+2) Open windbg preview as administrator by running `windbgx` in an elevated command prompt
233
+
234
+3) Navigate to `file` -> `Attach to process`
235
+
236
+4) Check `Record with Time Travel Debugging` (at the bottom right)
237
+
238
+4) Check `Show processes from all users` (at the bottom)
239
+
240
+5) Select `wslservice.exe`. Note, if wslservice.exe is not running, you make it start it with: `wsl.exe -l`
241
+
242
+6) Click `Configure and Record` (write down the folder you chose for the traces)
243
+
244
+7) Reproduce the issue
245
+
246
+8) Go back to windbg and click `Stop and Debug`
247
+
248
+9) Once the trace is done collecting, click `Stop Debugging` and close Windbg
249
+
250
+10) Go to the folder where the trace was colleced, and locate the .run file. It should look like: `wslservice*.run`
251
+
252
+11) Share that file on the issue
\ No newline at end of file