Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

Hardwired timeout in Static Driver Verifier?

Wilhelm_NökerWilhelm_Nöker Member Posts: 37

Hi all,

this is my first attempt ever to use SDV, and it's with a WDF driver that the verifier categorizes as "generic". (I suppose that's because it is a WSK client, or in other words, is linked against netio.lib, one of the "graylisted" libraries mentioned here.) I have Visual Studio 2019 (v16.3.9) and a recently downloaded WDK 1903, all running on Windows 10 v1903.

Anyway, no matter what I do, SDV always stops after roughly 50 minutes, and the GUI tells me that the rule checks were aborted by timeout. Things I've tried:

  1. Launching SDV from a command prompt instead of the GUI. This does provide helpful information, like the full path for two instances of sdv-default.xml being read (one from C:\Program Files (x86)\Windows Kits\10\Tools\SDV\data\generic\, one from my project directory) and the total time taken for analysis, but it doesn't change the outcome.

  2. Various timeout values entered in the GUI (like 10, 120 or 180 minutes). I can see that they are translated to the appropriate seconds value in my sdv-default.xml, but analysis always stops after 2980 seconds (plus/minus one or two).

  3. Launching SDV from an EWDK command prompt. I run LaunchBuildEnv.cmd from the mounted ISO image, then change to my project directory and run a batch file with the required MsBuild calls. This creates additional problems (some read-only files get placed in subfolders of my project directory, which MsBuild later doesn't know how to clean up, but fortunately "rd /s /q sdv" does), but I still get timeout after 50 minutes.

  4. Running SDV in debug mode gave me about 30K of console output to ponder, but no hints about the processing of my timeout value (or about the lack of it). Actually SDV doesn't even say "timeout" on the console (it's only the GUI that says so later on). What it does say after being quiet and busy for many, many minutes is:

    [DEBUG] cumulative exit code is 0
    [DEBUG] Reached ActionComplete of Master CheckRule - nullcheck
    [DEBUG] Done executing action for CheckRule - nullcheck
    [DEBUG] Could not find valid URL mapping for rule nullcheck

  5. And no, it's not a particular problem with the nullcheck rule. When I explicitly ask for the useafterfree rule, the total analysis time is only slightly different (closer to 2995 seconds rather than 2980).

  6. Still wondering where the unwanted timeout value came from, I took a look at the WDK default version of sdv-default.xml, from Tools\SDV\data\generic. Nothing suspicious there, SDV_SlamConfig_Timeout=86400, but even changing that value to, say, 5400 seconds doesn't do me any good.

Has anyone ever seen anything like this? Me, I'm stuck. SDV won't properly look at my driver, and I'm running out of ideas to try.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE