Automatically ignoring Driver Verifier error

NTDEV
1

This general questions relates to Driver Verifier.

DriverVerifier catches a bug in a component we are deveolping.
Fixing it is not trivial, and it will take a lot of thinking and a bit of re-designing.

My co-worker is working on it, but while he does that, I’m still developing the driver
and it’s important that I’ll keep test it.

I spend a lot of time making my tests automated, and they are.
The problem is that Driver Verifier BSOD my driver(because of the bug I’v told you about).

Theres an option in Windbg to Ignore the error, I used it today while testing manually with Windbg attached but I want to do it automatically on every test.

Is there a way? A config? Something I can do?

Thanks!

2

How about turning that test OFF in verifier. You can always turn it back on.

Gary G. Little

----- Original Message -----
From: xxxxx@hotmail.com
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 22, 2011 12:43:34 PM
Subject: [ntdev] Automatically ignoring Driver Verifier error

This general questions relates to Driver Verifier.

DriverVerifier catches a bug in a component we are deveolping.
Fixing it is not trivial, and it will take a lot of thinking and a bit of re-designing.

My co-worker is working on it, but while he does that, I’m still developing the driver
and it’s important that I’ll keep test it.

I spend a lot of time making my tests automated, and they are.
The problem is that Driver Verifier BSOD my driver(because of the bug I’v told you about).

Theres an option in Windbg to Ignore the error, I used it today while testing manually with Windbg attached but I want to do it automatically on every test.

Is there a way? A config? Something I can do?

Thanks!

—
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

But it’s not a single test. It’s a bunch of asserts.
I want to ignore one of them, not all of them.

If I’ll keep running those tests I’ll find bugs earlier.

4

wrote in message news:xxxxx@ntdev…
> But it’s not a single test. It’s a bunch of asserts.
> I want to ignore one of them, not all of them.
>
> If I’ll keep running those tests I’ll find bugs earlier.

Well, if you have windbg connected anyway, you can make a script
or extenstion which will intercept breakpoints, understand why it occurred
and auto resume.

If you watch the windbg list, recently there was a message about an
interesting python scripting framework, by the way.

–pa

5

Thanks, it’s sounds like a nice idea.

Windbg attached will make it harder to test on multiple machines simultaneously on the ESX server (because I’ll need to have a debugging machine for each machine), but It can help me automate the process If I’ll ran the tests synchronously on workstations.

6

wrote in message news:xxxxx@ntdev…

> Windbg attached will make it harder to test on multiple machines
> simultaneously on the ESX server (because I’ll need to have a debugging
> machine for each machine),

you can run several windbg’s on one host, connected to different com ports
(usb to serial, or LAN “telnet boxes”)

–pa

7

The VM case is even easier as you just need to create a different
named pipe for each vm.

Mark Roddy

On Fri, Mar 25, 2011 at 4:39 PM, Pavel A. wrote:
> wrote in message news:xxxxx@ntdev…
>
>> Windbg attached will make it harder to test on multiple machines
>> simultaneously on the ESX server (because I’ll need to have a debugging
>> machine for each machine),
>
> you can run several windbg’s on one host, connected to different com ports
> (usb to serial, or LAN “telnet boxes”)
>
> --pa
>
>
>
> —
> 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
>