KMDF Debugging Registry Values

NTDEV
1

would one normally put entries in their inf file for KMDF Debugging, i.e. VerifierOn, VerboseOn, DbgBreakOnError, etc., that they are going to deploy to customers?

i.e. should they be only used for development purposes only?

if only used for development purposes, what would happen if they were left in?

2

you should *NEVER* deploy your driver with these values on. VerifierOn can drastically affect perf. VerboseOn will increase the logging, removing entries that may be relevant on a crash. DbgBreakOnError will bugcheck the machine if a break is hit b/c there is no kernel debugger attached.

These are dev only values.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@ddc-web.com
Sent: Friday, November 16, 2007 10:29 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF Debugging Registry Values

would one normally put entries in their inf file for KMDF Debugging, i.e. VerifierOn, VerboseOn, DbgBreakOnError, etc., that they are going to deploy to customers?

i.e. should they be only used for development purposes only?

if only used for development purposes, what would happen if they were left in?

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

3

There is a tool in the 6001 WDK called WdfVerifier [ddkroot\tools\wdf]. It works on every version of KMDF ever shipped, and it will turn these settings on and off as needed without you having to g near your INF file. You can never typo a setting and you can never make inconsistent settings. It can manage settings for every KMDF driver on a machine. You can use it from one machine to control the verifier settings on another. If your driver(s) are PnP function and filter drivers, it can even enable and disable your devices so changed settings take effect.

It even does similar nice things for debugging UMDF drivers, including a few things that aren’t documented in the WDK last I looked.

It’s free [you just need to download the 6001 WDK]- why not use it?