[Applies to KMDF only]
The VERIFY_IS_IRQL_PASSIVE_LEVEL macro breaks into the kernel debugger if the driver is not executing at IRQL = PASSIVE_LEVEL.
This macro has no parameters.
The code for the VERIFY_IS_IRQL_PASSIVE_LEVEL macro is included in your driver's binary when you build your driver in a release configuration or a debug configuration. If your driver's binary includes VERIFY_IS_IRQL_PASSIVE_LEVEL code, the code will run when your driver runs with checked builds or free builds of the Microsoft Windows operating system.
The VERIFY_IS_IRQL_PASSIVE_LEVEL code breaks into a kernel debugger if one of the following is true:
- DbgBreakOnError is set to a non-zero value in the registry.
- VerifierOn is set to a non-zero value and DbgBreakOnError is not set.
- Driver Verifier is enabled, the driver was built with framework version 1.9 or later, and neither VerifierOn nor DbgBreakOnError is set.
For more information about registry entries that you can use to debug your driver, see Registry Entries for Debugging Framework-Based Drivers.
For more information about debugging your driver, see Debugging a KMDF Driver.
The following code example breaks into the kernel debugger if the driver is not executing at IRQL = PASSIVE_LEVEL.
Minimum KMDF version
|Wdfassert.h (include Wdf.h)|