Cannot perform TTD debugging with error message "Recording of failed unexpectedly"

[jamesWalker55]

I'm trying to do time-travel debugging with a faulty program (Reaper).

I launch the program manually, then use "Attach to process" to attach to the software. After some time I press "Stop and Debug", it fails and shows the error:

TDD recording encounter an error:
Recording of failed unexpectedly

Recording of the error for more context:

reaper_RyEde0jWaJ.mp4

[KenSykes]

If you open the log view and scroll down to where TTD is performing the recording, there should be an indication of an error and/or the location of the trace file. There are cases where windbg says this even though TTD does record successfully. We just checked in some changes that reduces the chance of that occuring as well. These changes should be available by end of the year.

[jamesWalker55]

When I check the log, I see the following:

EULA has been accepted.
Attaching to 38984
    Initializing the recording of process (PID:38984) on trace file: C:\Users\James\Documents\Kontakt Debugging\reaper10.run
    Recording has started of process (PID:38984) on trace file: C:\Users\James\Documents\Kontakt Debugging\reaper10.run
Warning:  Please see 'C:\Users\James\Documents\Kontakt Debugging\reaper10.out' for warning messages about your trace file

2024-11-10:14:15:13:745 : Error : DbgXUI.dll : TTD was not able to parse any process ID from the output of recording
2024-11-10:14:15:13:745 : Warning : DbgXUI.dll : TTD error: no PIDs were identified from the recorder's output
2024-11-10:14:15:13:745 : Warning : DbgXUI.dll : Microsoft (R) TTD 1.01.11 x64
Release: 1.11.429.0
Copyright (C) Microsoft Corporation. All rights reserved.


EULA has been accepted.
Attaching to 38984
    Initializing the recording of process (PID:38984) on trace file: C:\Users\James\Documents\Kontakt Debugging\reaper10.run
    Recording has started of process (PID:38984) on trace file: C:\Users\James\Documents\Kontakt Debugging\reaper10.run
Warning:  Please see 'C:\Users\James\Documents\Kontakt Debugging\reaper10.out' for warning messages about your trace file

2024-11-10:14:15:13:757 : Error : DbgXUI.dll : TTD trace file provided to load is empty or null
2024-11-10:14:15:13:757 : Error : DbgX.Services.dll : StopRecordAndDebugAsync failedSystem.ArgumentException: value cannot be null or empty (Parameter 'tracefilePath')
   at DbgXUI.Services.TtdRecordingService.LoadTracefileAndIndexAsync(String tracefilePath)
   at DbgXUI.Dialogs.RecordProgress.RecordDialog.StopRecordingAsync(Boolean loadTrace, CancellationToken token)
   at DbgX.Services.Utilities.TaskExtensionMethods.AwaitAndLog(Task task, String taskName)

When I check the folder, the files reaper10.out and reaper10.run do exist and have non-zero sizes. Does this mean TTD is recorded successfully?

[KenSykes]

Yes it does mean the recording is likely successful, you can open the trace file from the File menu. The fix should be available in January.