Null modem cable question

WINDBG
1

Hello,
I’m new to Windbg. The Windbg documentation says that the host and target
machines should be connected using a null modem serial cable. In my
development environment, I have the host and target machines connected via
the standard RJ45 ethernet cable. Is there a way to use this connection
for the debugging session with Windbg ?

Regards,
Sunil Jigyasu
VigorSoft Pvt Ltd,
Baroda, India.

2

No. You cannot use the ethernet for debugging using WinDbg. You can
either use Serial (with Null modem cable) or 1394 (on XP).

Rajiv.

-----Original Message-----
From: xxxxx@vigorsoft.com [mailto:xxxxx@vigorsoft.com]
Sent: Tuesday, March 04, 2003 6:34 PM
To: Kernel Debugging Interest List
Subject: [windbg] Null modem cable question

Hello,
I’m new to Windbg. The Windbg documentation says that the host and
target machines should be connected using a null modem serial cable. In
my development environment, I have the host and target machines
connected via the standard RJ45 ethernet cable. Is there a way to use
this connection for the debugging session with Windbg ?

Regards,
Sunil Jigyasu
VigorSoft Pvt Ltd,
Baroda, India.

You are currently subscribed to windbg as: xxxxx@wipro.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

3

Windbg and kd only support serial cable and 1394/Firewire debugging.
1394/Firewire is only supported on XP and above.

There is also a debugger option referred to as “local kernel debugging”
which allows you to inspect memory. This option is also available on XP
and above and is invoked by passing the -kl parameter to windbg or kd.
(Note: you cannot get stack traces using the -kl option.)

A 3rd party product called VMware allows you to run multiple OSes on the
same machine and allows you to use a “virtual serial port” for kernel
debugging. Documentation about how to configure it can be found at the
following location:

http://www.vmware.com/support/ws4/doc/devices_serial_ws.html
http://www.vmware.com/support/ws3/doc/ws32_devices3.html

There is a similar product Microsoft recently purchased from Connectix
Corp. called “Virtual PC”. I have heard of others who have tried this
product and it requires you to dedicate a serial port to it for kernel
debugging, just like standard kernel debugging. I can’t say at this
point if there is any hope it might support 1394/Firewire or any other
“faster” connection alternatives in the future.

There is a possibility that windbg will support USB 2.0 debugging in the
future. But from what I can tell, it is still a long ways off.

-----Original Message-----
From: Rajiv B.L. [mailto:xxxxx@wipro.com]
Sent: Tuesday, March 04, 2003 5:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Null modem cable question

No. You cannot use the ethernet for debugging using WinDbg. You can
either use Serial (with Null modem cable) or 1394 (on XP).

Rajiv.

-----Original Message-----
From: xxxxx@vigorsoft.com [mailto:xxxxx@vigorsoft.com]
Sent: Tuesday, March 04, 2003 6:34 PM
To: Kernel Debugging Interest List
Subject: [windbg] Null modem cable question

Hello,
I’m new to Windbg. The Windbg documentation says that the host and
target machines should be connected using a null modem serial cable. In
my development environment, I have the host and target machines
connected via the standard RJ45 ethernet cable. Is there a way to use
this connection for the debugging session with Windbg ?

Regards,
Sunil Jigyasu
VigorSoft Pvt Ltd,
Baroda, India.

You are currently subscribed to windbg as: xxxxx@wipro.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com