I am trying to setup kernel debug environment to debug printer driver installed on Vista 64 Bit.
My target system is Windows Vista 64 bit where the driver will be installed.
My host system is Windows XP 32 bit.
I am try to do serial port debugging.
Using bcdedit, I have enabled kernel debugging on Vista system and specified com 1 as the debug port.
Then I installed debugging tools for 32 bit on XP system.
After I reboot Windows Vista system, no connection is established with windbg launched on Windows XP 32 bit.
Another thing I noticed is that, com port is automatically uninstalled and doesnt show up in device manger after remote kernel debugging has been enabled in Vista.
Please help. If you have any idea or reference then kindly share it.
What is WinDbg reporting? Is it saying “waiting to reconnect?”
The first time you ran WinDbg after installation, did it give you a
“file not found” error, and tell you to restart.
Have you told WinDbg to break in? Just to make sure, try pressing
the pause button, assuming that you are getting “waiting to reconnect.”
I can’t say that I have used serial kd on Vista (I use 1394), but I
believe that the com port do being present in device manager is possibly
correct, although I would have thought it to be displayed as yellow. I
really don’t know about the serial case.
I am trying to setup kernel debug environment to debug printer driver
installed on Vista 64 Bit.
My target system is Windows Vista 64 bit where the driver will be
installed.
My host system is Windows XP 32 bit.
I am try to do serial port debugging.
Using bcdedit, I have enabled kernel debugging on Vista system and
specified com 1 as the debug port.
Then I installed debugging tools for 32 bit on XP system.
After I reboot Windows Vista system, no connection is established with
windbg launched on Windows XP 32 bit.
Another thing I noticed is that, com port is automatically uninstalled
and doesnt show up in device manger after remote kernel debugging has
been enabled in Vista.
Please help. If you have any idea or reference then kindly share it.
Thanks
You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Are you using WinDbg 6.7.0.5 (the most recent version) with the ‘-b’
option? If so, I have found that the presence of this option causes
WinDbg to fail to break in. If you have it, either remove it, or add
the ‘-d’ option to the command line. Microsoft is presently looking at
this problem.
I am trying to setup kernel debug environment to debug printer driver
installed on Vista 64 Bit.
My target system is Windows Vista 64 bit where the driver will be
installed.
My host system is Windows XP 32 bit.
I am try to do serial port debugging.
Using bcdedit, I have enabled kernel debugging on Vista system and
specified com 1 as the debug port.
Then I installed debugging tools for 32 bit on XP system.
After I reboot Windows Vista system, no connection is established with
windbg launched on Windows XP 32 bit.
Another thing I noticed is that, com port is automatically uninstalled
and doesnt show up in device manger after remote kernel debugging has
been enabled in Vista.
Please help. If you have any idea or reference then kindly share it.
Thanks
You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
I am trying to setup kernel debug environment to debug printer driver
installed on Vista 64 Bit.
My target system is Windows Vista 64 bit where the driver will be
installed.
My host system is Windows XP 32 bit.
I am try to do serial port debugging.
Using bcdedit, I have enabled kernel debugging on Vista system and
specified com 1 as the debug port.
Then I installed debugging tools for 32 bit on XP system.
After I reboot Windows Vista system, no connection is established with
windbg launched on Windows XP 32 bit.
Another thing I noticed is that, com port is automatically uninstalled
and doesnt show up in device manger after remote kernel debugging has
been enabled in Vista.
Please help. If you have any idea or reference then kindly share it.
In our experience, the #1 issue with kernel debugging over a serial port
is getting the right serial cable. What are you using? You need a
“null model” cable. If you have one of the old LapLink cables, they
also work very well.
One way to test this is to bring up both systems without the debugger,
then bring up HyperTerminal on each system on the appropriate serial
port with the appropriate speed, and make sure that keystrokes on one
machine are seen on the other machine.
By the way, it is normal behavior that the kernel debugger serial port
does not show up in device manager. The port is not actually available
to the operating system.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
In our experience, the #1 issue with kernel debugging over a serial port
is getting the right serial cable. What are you using? You need a
“null model” cable.
Fingers are a terrible thing to waste. “Null modem” cable, not “null
model”.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
My NULL modem cable has just 3 wires, RxD, TxD, & Ground (Data pins swapped
at each end of course).
It is actually possible to make such a cable rather than buying one - 2x
9-pin connectors and either short 3 core mains cable or a longer bit of twin
(separately screened) stereo audio cable should all be fine… (for those
of us who still feel a soldering iron has some use these days).
M
----- Original Message -----
From: jim
Newsgroups: windbg
To: Kernel Debugging Interest List
Sent: Tuesday, May 22, 2007 6:11 PM
Subject: Re:[windbg] Target Vista 64 bit and Host XP 32 bit - debugginf
Not only does it have to be null, but the flow control signals must be
properly wired.
This one works:
Belkin F3B207-10
I’ve gotten them from comp usa but if you Google it you will find them
widely available and dirt cheap (less than 3 bucks).
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com