OK… So I just did an ‘upgrade’ over my existing WinDBG install (6.1.9)
and now I’m having some issues…
-
Whenever I reboot the target machine, the initial connection to
WinDBG is made, but then the Text area where you would enter commands
into the “Command” window becomes active, as opposed to being grayed
out… so I have a blinking cursor, no “kd>” (just a gray square), and
the target continues booting… weird.
-
KdFiles is screwed. The system starts to copy over the driver file to
the target machine, and then locks up and jumps to 100% cpu usage.
Here’s a sample of the boot:
---- snip ----
Microsoft (R) Windows Debugger Version 6.1.0017.1
Copyright (c) Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Opened \.\DBG1394_INSTANCE01
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
symsrv*symsrv.dll*\jackson\wintools\symsrv;srv*\jackson\wintools\downloadstore*http://msdl.microsoft.com/download/symbols;d:\build\debug;d:\windbgsyms;d:\kernel\build\chk\i386;d:build\release
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
System Uptime: not available
*******************************************************************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for VIDEOPRT.SYS on Build 2600
pjHrZtqwFPtFbOxP3CwP0D
*
*******************************************************************************
KD: Accessing ‘D:\kernel\build\chk_w2k\i386\phmmini.sys’
(\SystemRoot\System32\Drivers\phmmini.sys)
File size 18K.
---- snip ----
WinDBG appears to ‘freeze’ at this point, and I sit at 100% CPU usage. I
can’t break into the target, WinDBG is essentially locked up at this
point, spinning happily away doing *something*.
At first I thought this was due to the upgrade and not having rebooted
after the upgrade, so I cold-booted the host machine, then cold-booted
the target machine, and got the same results…
This setup is exactly the same as what I had with 6.1.9, and it worked
just fine. The driver file being copied *does* exist and is accessible,
so it’s not like it’s stuck in a loop looking for the file.
Target:
Windows XP SP1
Host:
Windows XP (non-SP1)
Debugging Connection:
1394
Any thoughts???
sean
I have similar problem with 6.1.17.
– Kenny
-----Original Message-----
From: Sean Bullington [mailto:xxxxx@stg.com]
Sent: Thursday, December 19, 2002 3:27 PM
To: Kernel Debugging Interest List
Subject: [windbg] New Windbg bugs (6.1.17)???
OK… So I just did an ‘upgrade’ over my existing WinDBG
install (6.1.9)
and now I’m having some issues…
-
Whenever I reboot the target machine, the initial connection to
WinDBG is made, but then the Text area where you would enter commands
into the “Command” window becomes active, as opposed to being grayed
out… so I have a blinking cursor, no “kd>” (just a gray
square), and
the target continues booting… weird.
-
KdFiles is screwed. The system starts to copy over the
driver file to
the target machine, and then locks up and jumps to 100% cpu usage.
Here’s a sample of the boot:
---- snip ----
Microsoft (R) Windows Debugger Version 6.1.0017.1
Copyright (c) Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Opened \.\DBG1394_INSTANCE01
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
symsrv*symsrv.dll*\jackson\wintools\symsrv;srv*\jackson\wint
ools\downloadstore*http://msdl.microsoft.com/download/symbols;
d:\build\debug;d:\windbgsyms;d:\kernel\build\chk\i386;d:build\release
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
System Uptime: not available
**************************************************************
*****************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for VIDEOPRT.SYS on Build 2600
pjHrZtqwFPtFbOxP3CwP0D
*
**************************************************************
*****************
KD: Accessing ‘D:\kernel\build\chk_w2k\i386\phmmini.sys’
(\SystemRoot\System32\Drivers\phmmini.sys)
File size 18K.
---- snip ----
WinDBG appears to ‘freeze’ at this point, and I sit at 100%
CPU usage. I
can’t break into the target, WinDBG is essentially locked up at this
point, spinning happily away doing *something*.
At first I thought this was due to the upgrade and not having
rebooted
after the upgrade, so I cold-booted the host machine, then
cold-booted
the target machine, and got the same results…
This setup is exactly the same as what I had with 6.1.9, and
it worked
just fine. The driver file being copied *does* exist and is
accessible,
so it’s not like it’s stuck in a loop looking for the file.
Target:
Windows XP SP1
Host:
Windows XP (non-SP1)
Debugging Connection:
1394
Any thoughts???
sean
You are currently subscribed to windbg as: xxxxx@synaptics.com
To unsubscribe send a blank email to %%email.unsub%%
Same problem, except that my host AND target machines both run XP-SP1 and
the with 6.1.17. It was working prefectly with the previous windbg version
with the same os/hardware test platform.
Back to serial link…or back to the old windbg version, that i do not
have anymore… where can i get it?
Christophe
You should be able to grab it from:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.1.9.0.exe
Apparently they leave the old packages up on the server. If you can’t
grab it, I can send it to you. I’d post it but I don’t know the issues
with doing that (whether Microsoft would complain about redistribution,
etc.)
Always keep the older version around when upgrading, it saves alot of
headaches 
BTW: I did downgrade and all the 1394 stuff went back to working. I’ll
just wait for the next release before upgrading…
sean
xxxxx@sistech.fr wrote:
Same problem, except that my host AND target machines both run XP-SP1 and
the with 6.1.17. It was working prefectly with the previous windbg version
with the same os/hardware test platform.
Back to serial link…or back to the old windbg version, that i do not
have anymore… where can i get it?
Christophe
You are currently subscribed to windbg as: xxxxx@stg.com
To unsubscribe send a blank email to xxxxx@lists.osr.com