You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am recording trace for time travel debugging. And my program behaves differently when I record the trace and when I debug it normally.
I traced both executions and see that lodsd instruction preserves unused bits of RAX register when recording the trace.
When debug the same program with Visual Studio without recording the trace unused bits of RAX are zeroed.
Thanks for pointing this out. You're right, we did not fix LODSD in 1.11.410, we only fixed LODSB/W unfortunately. We will make a fix for this shortly.
I am recording trace for time travel debugging. And my program behaves differently when I record the trace and when I debug it normally.
I traced both executions and see that lodsd instruction preserves unused bits of RAX register when recording the trace.
When debug the same program with Visual Studio without recording the trace unused bits of RAX are zeroed.
Release notes for TTD 1.11.410 mention some fix about LODS but it does not look correct.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-release-notes#111410
The text was updated successfully, but these errors were encountered: