Kernel mode I/O breakpoint?

WINDBG
1

Hi all,

I’m trying to breakpoint on I/O port access, and I can’t seem to figure out
an incantation that WinDBG likes. I want to watch for reads of the ATA
status register, which is 1F7 on the primary ATA controller. If I do :

ba r1 1f7, that’s obviously going to fail, because that is awaiting a read
(or a write, if the WinDBG 2.0.11 Beta docs are to be believed), on memory
address 1F7. So I try:
ba I1 1f7, which yields:
I/O breakpoints not enabled
So I try multiple combinations of sizes and addresses, and combinations of i
and r. Nothing doing. Is this thing telling me I can’t breakpoint on an
I/O port with WinDBG? Or is it a limitation on the kernel debugger in
Windows NT and Windows 2000?

Thanks, I hope,

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

IO breakpoints are a feature of the kernel. Currently the only OS that
supports them is Whistler. So if you are debugging Whistler Beta 1 then
you can use them.

Sorry

-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Wednesday, December 13, 2000 1:05 PM
To: Kernel Debugging Interest List
Subject: [windbg] Kernel mode I/O breakpoint?

Hi all,

I’m trying to breakpoint on I/O port access, and I can’t seem to figure
out
an incantation that WinDBG likes. I want to watch for reads of the ATA
status register, which is 1F7 on the primary ATA controller. If I do :

ba r1 1f7, that’s obviously going to fail, because that is awaiting a
read
(or a write, if the WinDBG 2.0.11 Beta docs are to be believed), on
memory
address 1F7. So I try:
ba I1 1f7, which yields:
I/O breakpoints not enabled
So I try multiple combinations of sizes and addresses, and combinations
of i
and r. Nothing doing. Is this thing telling me I can’t breakpoint on
an
I/O port with WinDBG? Or is it a limitation on the kernel debugger in
Windows NT and Windows 2000?

Thanks, I hope,

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Bummer. Thanks for the answer, anyway. Phil

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Wednesday, December 13, 2000 2:23 PM
To: Kernel Debugging Interest List
Cc: xxxxx@intel.com
Subject: [windbg] RE: Kernel mode I/O breakpoint?

IO breakpoints are a feature of the kernel. Currently the only OS that
supports them is Whistler. So if you are debugging Whistler Beta 1 then
you can use them.

Sorry

-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Wednesday, December 13, 2000 1:05 PM
To: Kernel Debugging Interest List
Subject: [windbg] Kernel mode I/O breakpoint?

Hi all,

I’m trying to breakpoint on I/O port access, and I can’t seem to figure
out
an incantation that WinDBG likes. I want to watch for reads of the ATA
status register, which is 1F7 on the primary ATA controller. If I do :

ba r1 1f7, that’s obviously going to fail, because that is awaiting a
read
(or a write, if the WinDBG 2.0.11 Beta docs are to be believed), on
memory
address 1F7. So I try:
ba I1 1f7, which yields:
I/O breakpoints not enabled
So I try multiple combinations of sizes and addresses, and combinations
of i
and r. Nothing doing. Is this thing telling me I can’t breakpoint on
an
I/O port with WinDBG? Or is it a limitation on the kernel debugger in
Windows NT and Windows 2000?

Thanks, I hope,

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com