The FAQ should say upgrade to v6.5. This was a bug in the 6.4 debugger.
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Tuesday, July 19, 2005 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Problem with WinDbg
This question seems to arise periodically; maybe we need an FAQ.
Jason’s answer last time:
Sent: Tuesday, June 14, 2005 9:35 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Kernel Debugging - IA64
Look for a file in your system32 directory named kldbgdrv.sys and delete
it, then launch kd again.
Jason
While he refers to kd, the same information applies to WinDBG (same
debugger engine, different interfaces).
Hope this helps.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gorodilov Alexei
Sent: Tuesday, July 19, 2005 2:13 PM
To: Kernel Debugging Interest List
Subject: [windbg] Problem with WinDbg
Hi,
When I start local kernel debugging WinDbg prints message:
The sytem does not support local kernel debugging. Local kernel
debugging
requires Windows XP, Administrative privileges, and is not supported by
WOW64.
Only a single local kernel debugging session can run at a time.
and then close debug session. I have Administrative privileges.
system: Windows 2003 sp1
WinDbg: 6.4.0007.0
Regards
Alexei Gorodilov
You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com