Serial debugging of Windbg does not work through virtual serial port

I have the following configuration:

Operating System: Windows 7 SP1 Guest OS: Windows XP SP3 Pro

guest OS runs on VMWare version 7 workstation

I configured a virtual serial port on a virtual machine like "output named pipe" and the following name:

\\.\pipe\whatever 

I also added the appropriate parameters to the boot.ini file on the Win XP SP3 Pro image to enable debugging (/ debugport = com1 baudrate = 115200)

in windbg, I am setting up the Kernel Debugging option, going to:

File-> Kernel Debugging

and selecting the COM tab and configure as follows:

Providing a port name as:

 \\.\pipe\whatever 

and checking the Pipe window.

I load the Windows XP SP3 virtual machine and select the second entry in which debugging mode is enabled. Right after that, I click Ok inside Windbg to start a kernel debugging session.

But even then, it remains stuck in the following message:

Open \. \ Pipe \ whatever Waiting for reconnection ...

It says: "Debuggee not connected" and remains in this message even after Virtual Machine is fully loaded. The virtual serial port status in VmWare is also displayed as Connected.

I checked the network connections.

The virtual machine has a network adapter in bridge mode, and I can successfully perform a successful check of the guest OS and host system.

+4
source share
4 answers

Probably your problem is that WinDbg does not break the connection, so it is connected, but it does not talk about it, and you think that it does not work.

I was lucky with WinDbg on the command line with -b, although I noticed that this option could be removed in subsequent builds. I tested 6.12.0002.633 x86.

  windbg -b -k com:pipe,port=\\.\pipe\com_1 

(From here .)

+2
source

I had the same problem, and after changing the port on your Windows guest (in vmware) you should be connected. In my case, the port in boot.ini was com1 , and I changed it to com2 .

+1
source

Have you also included / debug in boot.ini?

0
source

This may be your VMWare serial port configuration. The configuration should be:

Use named pipe: \. \ Pipe \ whatever This target is the server. The other end is the application.

It is necessary to check the processor efficiency during the survey.

More details here: http://www.vmware.com/support/ws5/doc/ws_devices_serial_advanced_example_debugging.html

0
source

Source: https://habr.com/ru/post/1389521/


All Articles