WinDbg Connection problem

[Joel]

Hi,

I am trying to configure a remote debug session through a serial cable (
COM1 to COM1 ), of some reason the host computer doesn't respond to the
debugger, following is a flow of the actions taken:

-Step 01
( 1 ) The two computers are connect with a NULL modem cable
( 2 ) Hyper terminal was used to verify the connection integrity.
*Result: Text typed in the client computer is presented at the host computer
=> the connection is valid

-Step 02
( 1 ) WinDbg is executed on the client computer and tries to connect to the
host computer ( COM1, Baud=115200 )
( 2 ) The Host computer runs Hyper Terminal that 'listens' on the port
WinDbg tries to connect.
*Result: The host computer shows the connection queries sent by WinDbg =>
The client side ( the debugger ) works as expected.

-Step 03
( 1 ) Configure boot.ini with an additional entry for debugging:
"multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /debug /debugport=COM1 /baudrate=115200"
( 2 ) On the client: Run WinDbg and try to connect to COM1 ( local COM1 )
with baud of 115200.
( 3 ) restart the host computer, Boot with debug.
*Result: WinDbg SHOULD establish the connection upon host start up BUT this
doesn't happen.

Why can't I establish a remote debugging session?
What did I do wrong here?

ThanX
Nadav.

 

[Maxim S. Shatskih]

*Result: WinDbg SHOULD establish the connection upon host start up BUT this

doesn't happen.

Hit Ctrl+Break in WinDbg several times.

 

[Jeff Henkels]

Hit Ctrl+Break in WinDbg several times.

Will the Ctrl+Break trick work with a named pipe connection, too? I've been
having lots of trouble debugging VMWare virtual machines, in that WinDbg
very rarely sees the pipe.

 

[Maxim S. Shatskih]

Will the Ctrl+Break trick work with a named pipe connection, too? I've been

having lots of trouble debugging VMWare virtual machines, in that WinDbg
very rarely sees the pipe.

In my experience, I need to restart WinDbg each time Windows inside VMWare
reboots. So, first the "virtual Windows" must boot and stall waiting for a
debugger to connect (it waits for several seconds) - and at this moment you
must start WinDbg.

 

[Sel]

If you experience problem with WinDbg connection using serial...Try Firewire
connection... It works without any problem. And in cases where it doesnt
connect all i have to do is unplug the firewire cable and plug it back.
Other benefit is that its much faster than serial connection.