When will windbg support local kernel debugging for ia64 and amd64?
Ken
Is should do so today. What error do you see?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
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
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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</mk:>
Are you running the native 64 bit windbg on the 64bit box?
Calvin Guan??? Software Engineer??
ATI Technologies Inc. www.ati.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: March 14, 2005 2:11 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd.? This should be consistent
for all architectures.? Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today.? What error do you see?
?
Jason
?
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
?
When will windbg support local kernel debugging for ia64 and amd64?
?
Ken
?
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
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
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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</mk:>
Yes
-----Original Message-----
From: Calvin Guan [mailto:xxxxx@ati.com]
Sent: Monday, March 14, 2005 2:19 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you running the native 64 bit windbg on the 64bit box?
Calvin Guan??? Software Engineer??
ATI Technologies Inc. www.ati.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: March 14, 2005 2:11 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd.? This should be consistent
for all architectures.? Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today.? What error do you see?
?
Jason
?
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
?
When will windbg support local kernel debugging for ia64 and amd64?
?
Ken
?
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
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
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
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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</mk:>
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message from
the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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</mk:>
Ahh yes. Well you need to do the equivalent of adding /debug to
boot.ini on the ia64. This tells the kernel that a debugger will
potentially be attached, so it tracks some extra things, such as track
debug print messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message
from the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
Yeah, I just found that tool and info about how to use it.
I’ll give that a try.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 7:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ahh yes. Well you need to do the equivalent of adding /debug to boot.ini on
the ia64. This tells the kernel that a debugger will potentially be
attached, so it tracks some extra things, such as track debug print
messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message from
the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
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</mk:>
This is horrible. All that just to have to type !dbgprint to see what is in
the 4k buffer. Even then it doesn’t seem to appear for a while. How
frustrating!
I have something I need to debug on this ia64 system that has no serial or
firewire ports. Dbgview and dbgmon don’t run so I was hoping local debug
would capture debug output like normal. Given that I need to debug my
problem with dbgprint is there some other way to do this?
Thanks for your help getting this to work (so to speak).
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 7:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ahh yes. Well you need to do the equivalent of adding /debug to boot.ini on
the ia64. This tells the kernel that a debugger will potentially be
attached, so it tracks some extra things, such as track debug print
messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message from
the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
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</mk:>
So am I assuming you got the dbgprint working?
If I’m reading the issue correctly, it is that you are attempting to
perform kernel debugging on a system which is not configured for kernel
debugging. My understanding is that the 4k buffer doesn’t exist in the
kernel without the /debug switch, which is probably why dbgview did not
work.
The same article in debugger.chm mentioned before, titled “Performing
Local Kernel Debugging”, mentions both the /debug requirement and the
need for !dbgprint. The need to delete the kldbgdrv.sys file is a bug
in the debugger, and will be fixed in the next version. In addition, I
believe after deleting the file, ‘kd -kl’ should display “WARNING: Local
kernel debugging requires booting with /debug to work optimally.”. Was
this message not displayed?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 5:10 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
This is horrible. All that just to have to type !dbgprint to see what is
in the 4k buffer. Even then it doesn’t seem to appear for a while. How
frustrating!
I have something I need to debug on this ia64 system that has no serial
or firewire ports. Dbgview and dbgmon don’t run so I was hoping local
debug would capture debug output like normal. Given that I need to debug
my problem with dbgprint is there some other way to do this?
Thanks for your help getting this to work (so to speak).
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 7:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ahh yes. Well you need to do the equivalent of adding /debug to
boot.ini on the ia64. This tells the kernel that a debugger will
potentially be attached, so it tracks some extra things, such as track
debug print messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message
from the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>
Yes, I got it working. But this buffer thing is very ackward. As message
don’t come out right away.
Are you saying if I use /debug that dbgview would then work on the is64?
Thanks,
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 8:36 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
So am I assuming you got the dbgprint working?
If I’m reading the issue correctly, it is that you are attempting to perform
kernel debugging on a system which is not configured for kernel debugging.
My understanding is that the 4k buffer doesn’t exist in the kernel without
the /debug switch, which is probably why dbgview did not work.
The same article in debugger.chm mentioned before, titled “Performing Local
Kernel Debugging”, mentions both the /debug requirement and the need for
!dbgprint. The need to delete the kldbgdrv.sys file is a bug in the
debugger, and will be fixed in the next version. In addition, I believe
after deleting the file, ‘kd -kl’ should display “WARNING: Local kernel
debugging requires booting with /debug to work optimally.”. Was this
message not displayed?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 5:10 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
This is horrible. All that just to have to type !dbgprint to see what is in
the 4k buffer. Even then it doesn’t seem to appear for a while. How
frustrating!
I have something I need to debug on this ia64 system that has no serial or
firewire ports. Dbgview and dbgmon don’t run so I was hoping local debug
would capture debug output like normal. Given that I need to debug my
problem with dbgprint is there some other way to do this?
Thanks for your help getting this to work (so to speak).
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 7:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ahh yes. Well you need to do the equivalent of adding /debug to boot.ini on
the ia64. This tells the kernel that a debugger will potentially be
attached, so it tracks some extra things, such as track debug print
messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message from
the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if you
try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges, and
is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be consistent
for all architectures. Here’s a little snippet from the debugger.chm in the
article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be displayed
with the
mk:.chm::/hh/r26_exts_kernel_a_9hwn.htm> !dbgprint extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
_____
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
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
—
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</mk:>
I’ve never used dbgview, so I can’t say for sure. But my understanding
is that the kernel responds to /debug by enabling certain ‘features’
which are specific to debugging. So I’m inferring that dbgview works by
looking at the kernel structures (the dbgprint buffer) which will only
be around when /debug is enabled.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Tuesday, March 15, 2005 6:54 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, I got it working. But this buffer thing is very ackward. As message
don’t come out right away.
Are you saying if I use /debug that dbgview would then work on the is64?
Thanks,
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 8:36 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
So am I assuming you got the dbgprint working?
If I’m reading the issue correctly, it is that you are attempting to
perform kernel debugging on a system which is not configured for kernel
debugging. My understanding is that the 4k buffer doesn’t exist in the
kernel without the /debug switch, which is probably why dbgview did not
work.
The same article in debugger.chm mentioned before, titled “Performing
Local Kernel Debugging”, mentions both the /debug requirement and the
need for !dbgprint. The need to delete the kldbgdrv.sys file is a bug
in the debugger, and will be fixed in the next version. In addition, I
believe after deleting the file, ‘kd -kl’ should display “WARNING: Local
kernel debugging requires booting with /debug to work optimally.”. Was
this message not displayed?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 5:10 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
This is horrible. All that just to have to type !dbgprint to see what is
in the 4k buffer. Even then it doesn’t seem to appear for a while. How
frustrating!
I have something I need to debug on this ia64 system that has no serial
or firewire ports. Dbgview and dbgmon don’t run so I was hoping local
debug would capture debug output like normal. Given that I need to debug
my problem with dbgprint is there some other way to do this?
Thanks for your help getting this to work (so to speak).
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 7:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ahh yes. Well you need to do the equivalent of adding /debug to
boot.ini on the ia64. This tells the kernel that a debugger will
potentially be attached, so it tracks some extra things, such as track
debug print messages. I believe the ‘bootcfg’ tool can do this for you.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 4:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
As far as /debug there is no boot.ini file on the ia64 that I can find.
I’m not getting any debug output at all. Except to the initial message
from the debugger.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 6:40 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Are you booting /debug? Do you get any debug output?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Ok, that got the local debugging working but after entering !dbgprint I
still don’t get any debug output from my driver.
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 4:32 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Delete the kldbgdrv.sys file and it should start working again.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 1:29 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Yes, there is a kldbgdrv.sys in system32.
Yes, I downloaded the 64-bit debugger from the website.
When I type “kd -kl” at a command line:
I get the same messages as before plus:
Debuggee initialization failed, HRESULT 0x80004001
“Not implemented”
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 2:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is there a kldbgdrv.sys sitting in %WINDIR%\system32? Are you using the
32-bit debugger in WOW, or the 64-bit native debugger? Does it work if
you try kd instead of windbg?
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 11:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
On ia64 I get the following:
I Select File/Kernel Debug/Local Tab and Hit OK.
I get a pop up that says: The system does not support local kernel
debugging.
The command window says:
Microsoft … Version 6.4.0007.2
Copyright …
The sysmte does not support local kernel debugging.
Local kernel debugging requires Windows AP, Administrative priviledges,
and is not supported by WOW64.
Only a single local kernel debugging session can run at a time.
So just what is the problem?
Ken
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Monday, March 14, 2005 12:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Debug messages do not show through in local kd. This should be
consistent for all architectures. Here’s a little snippet from the
debugger.chm in the article titled “Performing Local Kernel Debugging”:
Kernel-mode drivers and Windows itself often send messages to the kernel
debugger by using DbgPrint and related functions. These messages are not
automatically displayed during local kernel debugging. They can be
displayed with the !dbgprint
mk:gger.chm::/hh/r26_exts_kernel_a_9hwn.htm> extension, however.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, March 14, 2005 9:11 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
I see no debug messages from my driver.
From: Jason Shay [mailto:xxxxx@winse.microsoft.com]
Sent: Friday, March 11, 2005 3:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Local Mode in ia64 and amd64
Is should do so today. What error do you see?
Jason
________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Thursday, March 10, 2005 12:18 PM
To: Kernel Debugging Interest List
Subject: [windbg] Local Mode in ia64 and amd64
When will windbg support local kernel debugging for ia64 and amd64?
Ken
—
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
—
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
—
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
—
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
—
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
—
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
—
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
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</mk:>