Automatically Launch Debugging for UMDF Drivers
It is not always safe to attach a user-mode debugger to a running host process. For example, if the host process, with global settings indicating that debugging was not going to take place, was started, the process could be terminated unexpectedly. This is possible if a critical I/O event occurs (such as Plug and Play (PnP) and power events) while the process is suspended by the debugger.
While WDF Verifier does support this form of debugging (and it is safe if debugging settings are turned on when the process starts), it also supports an automatic launching feature that prevents this problem.
To set up automatic launching of the debugger
Specify a minimum of 2 seconds for new host processes to wait before attaching the debugger. It is common for developers to want this wait time to occur when their driver is loaded, but you can specify that you want this to happen when the process starts.
Click Apply to save these settings.
Select Automatically launch user-mode debugger when requested.
Leave WDF Verifier running. When a new host process starts, WDF Verifier will automatically attach your preferred debugger to the process soon after it starts.
If your driver is already running, you can force it to be stopped and restarted by changing the UMDF trace level or by selecting Send Log Output to Kernel Debugger and then clicking Apply. This stops and starts all UMDF processes unless you have turned off the auto-restart feature (you can restore it on the Tool Preferences page).
Build date: 11/16/2013