Skip to content

Latest commit

 

History

History
79 lines (55 loc) · 2.22 KB

verify-is-irql-passive-level.md

File metadata and controls

79 lines (55 loc) · 2.22 KB
Raw
title description keywords ms.date ms.topic
VERIFY_IS_IRQL_PASSIVE_LEVEL Macro
The VERIFY_IS_IRQL_PASSIVE_LEVEL macro breaks into the kernel debugger if the driver is not executing at IRQL PASSIVE_LEVEL.
VERIFY_IS_IRQL_PASSIVE_LEVEL macro
08/23/2017
reference

VERIFY_IS_IRQL_PASSIVE_LEVEL macro

[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.

Syntax

VOID VERIFY_IS_IRQL_PASSIVE_LEVEL(void);

Parameters

This macro has no parameters.

Return value

None

Remarks

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.

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.

Examples

The following code example breaks into the kernel debugger if the driver is not executing at IRQL = PASSIVE_LEVEL.

VERIFY_IS_IRQL_PASSIVE_LEVEL();

Requirements

Target platform

 Universal

Minimum KMDF version

1.0

Header

 Wdfassert.h (include Wdf.h)

See also

WDFVERIFY