![2870.image001_5F00_thumb_5F00_06064C73.png 2870.image001_5F00_thumb_5F00_06064C73.png](http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-77-00-metablogapi/2870.image001_5F00_thumb_5F00_06064C73.png)
Hello ntdebugging readers, the Debug Ninja is back again with a quick blog this holiday season. I recently encountered a situation where the kernel debugger could not connect to a Windows Server 2008 R2 system running in a Hyper-V virtual machine. The configuration appeared correct; however, the debugger would not connect to the VM. In windbg you can use Ctrl+Alt+D to view the debugger’s internal information flow. In KD use Ctrl+D followed by ENTER to toggle the output. Enabling this output I could see that the debugger was unable to read from the debug port, and that it was getting timeouts. The error "SYNCTARGET: Timeout." is a clear indication that the debug host cannot communicate with the debug target, especially when this error appears after a “Send Break in” message. Read more: Ntdebugging Blog
QR:
0 comments:
Post a Comment