New answers tagged

0

I did not have the latest release of WinDbg but while debugging a 32-bit EXE, adding the WinDbgx64 directory to the PATH environment solved this problem. I solved this problem by configure the window PATH environment variable to point to the WinDbg64 for and not the x86 version. Thanks This Two Answer is helpful for me


0

You need to use the correct ethernet cable. If you are connecting target directly to your debugger host you need to use a cross over cable, not a regular ethernet cable. Alternately if you don't have a crossover a cable using a switch/hub is required to connect the devices. I'd check TCP/IP communication is working between devices prior to enabling debugging ...


Top 50 recent answers are included