Quantcast
Channel: WinDbg loses connection debugging over network, and target machine freeze - Stack Overflow
Browsing all 6 articles
Browse latest View live

Answer by shaked cohen for WinDbg loses connection debugging over network,...

I found a simpler solution that worked for me in VMware, The problem is in vmware - the NAT connection has a 30 seconds timeout. This value is configurable. Go to edit -> virtual network editor...

View Article



Answer by Ivellios for WinDbg loses connection debugging over network, and...

I also met this issue, and found that when I try to force shutdown VMWare OS, the windbg connection seems recover before VMWare OS is actually closed. After several tries, I found a weird solution:...

View Article

Answer by Girish BR for WinDbg loses connection debugging over network, and...

I had the similar problem and solved it by using USB to Ethernet adapter on the host machine instead of in built NIC card.

View Article

Answer by tchau.dev for WinDbg loses connection debugging over network, and...

I finally solved this problem by switching the host system. In the beginning, I thought the target system was the problem, because MSDN only put the NIC debug requirement on the target system. It...

View Article

WinDbg loses connection debugging over network, and target machine freeze

I'm trying to get WinDbg debugging over the network to work, but it always loses connections after I break into the debugger (Debug->Break), and then try to start it again (Debug->Go). However,...

View Article


Answer by Avinash Kumar Ranjan for WinDbg loses connection debugging over...

The problem is with the host. If you don't want to change your host and continue debugging on it, you might want to try using a serial port. It gives better performance. Take a look at the following...

View Article
Browsing all 6 articles
Browse latest View live




Latest Images