PAGED_CODE macro, WDK 6000, and XP

I have been getting “EX: Pageable code called at IRQL” debug messages in one
of my drivers. I finally figured out that the message was from the
PAGED_CODE macro. The driver displayed the message but did not ASSERT. The
macro uses NT_ASSERT instead of ASSERT. There is an OSR article about
NT_ASSERT.
I changed the macro to use ASSERT instead of NT_ASSERT and now my driver
asserts. So, it looks like the PAGED_CODE macro is useless. I didn’t try
running under Vista.

Bill Wandel

I am investigating this change, I will let you know what I find.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Friday, August 03, 2007 3:07 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] PAGED_CODE macro, WDK 6000, and XP

I have been getting “EX: Pageable code called at IRQL” debug messages in
one
of my drivers. I finally figured out that the message was from the
PAGED_CODE macro. The driver displayed the message but did not ASSERT.
The
macro uses NT_ASSERT instead of ASSERT. There is an OSR article about
NT_ASSERT.
I changed the macro to use ASSERT instead of NT_ASSERT and now my driver
asserts. So, it looks like the PAGED_CODE macro is useless. I didn’t try
running under Vista.

Bill Wandel


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

This should be fixed for the next WDK. Thanks for pointing this out!

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Friday, August 03, 2007 3:07 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] PAGED_CODE macro, WDK 6000, and XP

I have been getting “EX: Pageable code called at IRQL” debug messages in
one
of my drivers. I finally figured out that the message was from the
PAGED_CODE macro. The driver displayed the message but did not ASSERT.
The
macro uses NT_ASSERT instead of ASSERT. There is an OSR article about
NT_ASSERT.
I changed the macro to use ASSERT instead of NT_ASSERT and now my driver
asserts. So, it looks like the PAGED_CODE macro is useless. I didn’t try
running under Vista.

Bill Wandel


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Thanks.

Bill Wandel

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]
On Behalf Of Doron Holan
Sent: Thursday, August 09, 2007 7:10 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] PAGED_CODE macro, WDK 6000, and XP

This should be fixed for the next WDK. Thanks for pointing this out!

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Friday, August 03, 2007 3:07 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] PAGED_CODE macro, WDK 6000, and XP

I have been getting “EX: Pageable code called at IRQL” debug messages in one
of my drivers. I finally figured out that the message was from the
PAGED_CODE macro. The driver displayed the message but did not ASSERT.
The
macro uses NT_ASSERT instead of ASSERT. There is an OSR article about
NT_ASSERT.
I changed the macro to use ASSERT instead of NT_ASSERT and now my driver
asserts. So, it looks like the PAGED_CODE macro is useless. I didn’t try
running under Vista.

Bill Wandel


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer