It should only get replaced every time you attempt local kernel
debugging from WinDbg or kd. The driver allows lkd to do the magic it
does. The need to manually delete it is a WinDbg bug, and will be fixed
in the next version (coming soon!).
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Basrur, Girish
Aithal (STSD)
Sent: Tuesday, June 14, 2005 11:11 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Kernel Debugging - IA64
Hi Jason,
This works. Thanks a lot. Can you please tell me what this
driver is and how deleting it would enable local debugging? Also, I find
that this file gets replaced every time I reboot the machine.
Regards,
Girish.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
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
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@attotech.com
Sent: Tuesday, June 14, 2005 6:48 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Kernel Debugging - IA64
Odd… actually the /debug option *doesn’t* work on my system either,
but using “/debugport=com1 /baudrate=115200” does…
I don’t know why that’s happening, its definitely not in line with the
documentation.
Jason
xxxxx@lists.osr.com wrote on 06/14/2005 09:03:53 AM:
Thanks Jason,
I have already set the /DEBUG option using bootcfg.exe.
I presume that “native IA64 build of Windbg” you are referring to
the windbg build for IA64 systems, which is what I have downloaded
from the MS website.
Regards,
Girish.
From: xxxxx@lists.osr.com [mailto:
xxxxx@lists.osr.com] On Behalf Of xxxxx@attotech.com
Sent: Tuesday, June 14, 2005 6:28 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Local Kernel Debugging - IA64
You need to get the native IA64 build of Windbg, and make sure the
kernel is loaded with /DEBUG (use bootcfg.exe)
Jason
xxxxx@lists.osr.com wrote on 06/14/2005 04:28:57 AM:
> Hi,
> I am trying to capture the traces printed by my driver during
> boot, on an IA64 (Windows Server 2003 SP1) system. Since the system
> is at a remote location, I do not have a debugger connected to it.
> As such, I tried to use DbgView, but looks like there is no
> supported version of DbgView on IA64. My next option was Windbg set
> to local kernel debugging. However, with 6.4.7.2 version of Windbg,
> I get the following error whenever I start the local kernel
debugging option:
>
> “The system 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.”
>
> Can somebody help me out with this? Or is there any other utility
> that I can use on IA64 system which can capture the traces that are
> generated at boot time?
>
> Regards,
> Girish.
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
> To unsubscribe send a blank email to
xxxxx@lists.osr.com —
You are currently subscribed to windbg as: xxxxx@attotech.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
You are currently subscribed to windbg as: girish.aithal.basrur@hp.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
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com