Open ghost opened 2 years ago
For what it's worth, I also experience this issue with the 'wt' command in kernel debugging sessions. (Confirmed in the following configurations: Host:VM->Target:VM; Host:Physical->Target:VM; and Host:VM->Target:Physical (over USB), all running updated versions of Windows 10.) Though the docs suggest that 'wt' is supported over kernel connections, I haven't been able to execute it via any version of WinDbg, from Classic, through Preview and now the latest non-Preview WPF offering. (Does the latter have an official name?)
I have written a very rough script using the JS API to somewhat emulate the 'wt' command, although it's far from perfect. It is painfully slow, occasionally renders the debugger inoperable by inducing infinite loops in the target (seems to be related to interrupt-handling, or the lack thereof,) and, frankly, as a toy project for personal use, could do with a fair bit of cleaning up. If there's any interest in this script (and I can find it again,) I may be persuaded to share it.
I've also had this problem, and I can't find any information about it on the internet. Does anyone have a solution?
I am running Windows 11 Enterprise Build 22000.856 on VMWare and connected to it through COM port for kernel debugging and it is the latest version of windbg whenever I try to use the 'wt' command it shows ^ Unimplemented error in 'wt'.