I am using Windbg 6.5.0003.7 on a Windows XP 5.1 (Build
2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2)
When starting Windbg from the UI using Ctrl K for kernel Debug, I choose the
COM option. However the debug session starts for 1394 with
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Opened \.\DBG1394_INSTANCE44
Waiting to reconnect…
I have used COM debugging on this host machine before and neither Windbg
version nor the OS version has changed. This seems just out of the blue. Let
me know if anybody else has had a repro like this. Effectively my serial
debugging is cut out.
You probably have 1394 settings saved in your workspace. Check in Clear
Workspace, or just delete your workspaces by using Delete Workspaces (or
just delete HKCU\Software\Microsoft\Windbg\Workspaces to completely
scorch everything).
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of bank kus
Sent: Tuesday, November 15, 2005 6:45 PM
To: Kernel Debugging Interest List
Subject: [windbg] Trouble using COM debugging - Windbg
I am using Windbg 6.5.0003.7 on a Windows XP 5.1 (Build
2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2)
When starting Windbg from the UI using Ctrl K for kernel Debug, I choose
the COM option. However the debug session starts for 1394 with
Microsoft (R) Windows Debugger Version 6.5.0003.7 Copyright (c)
Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Opened \.\DBG1394_INSTANCE44
Waiting to reconnect…
I have used COM debugging on this host machine before and neither
Windbg version nor the OS version has changed. This seems just out of
the blue. Let me know if anybody else has had a repro like this.
Effectively my serial debugging is cut out.
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com