Re: PREfast (5744) fails some WDF headers, and thus my code too

Also your driver does not have to pass prefast with no errors or warnings.
They just want to see what errors are being flagged. I suspect they will
require a clean prefast sometime in the future, but not thus far.

"Dan" <d.murphy@xxxxxxxxxxxx> wrote in message
news:1162387817.231714.283590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
According to the DTM documentation you do not have to submitt the XML
file as this may contain IP that you may not want to show or have
Microsoft own.

From the help file:
"Because the standard PFD log file, Defects.xml, might contain
intellectual properly from your driver source code, you have to submit
only the summary results file, DefectsSum.txt, which does not contains
intellectual property."

There well crafted WHQL legal agreements are pretty clear that if you
share IP

THEY OWN IT!!!!

So submitting the XML file should not be required.

And yes they did indicate that it failed because of Prefast. So I will
give you a towel to clean up after your blood vessel pops

Dan

David J. Craig wrote:
You have to submit the xml file and not the txt file to pass prefast.

<chris.aseltine@xxxxxxxxx> wrote in message
news:1162341108.478529.36250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ray Trent wrote:

The point is to get people to at least run Prefast on their drivers.
What they do with that information is up to them.

Well, Winqual failed our submission today. Of course, they don't say
why anywhere on the site (at least that I can see), so we have to email
the winqual alias and wait, wait, wait...

If they say it's because of PREfast failures I think I'm going to pop a
blood vessel.




.

Relevant Pages

  • Re: what should I select when install HCT for testing NDIS protoco
    ... Since my driver will run on Win2K, I guess CUV is not an option for my case. ... build my driver with Windows Server 2003 SP1 DDK instead of Win2K DDK, ... Tools like PreFast analyze your code at build time and can catch some errors before you even run your code. ... When you install the WS2003 DDK the installer allows you to select the build enviroments that it will install. ...
    (microsoft.public.development.device.drivers)
  • Re: Build
    ... I'm curious if PREfast will work with #include "bla.c". ... Last year a customer sent me a driver not using ... does not follow the Microsoft blessed environement. ...
    (microsoft.public.development.device.drivers)
  • Re: Mutual exclusion at passive level
    ... source code access and can ask the owner of a driver stack about the rules, ... when almost all documentation on Windows 9x and MS-DOS was from third party ... developers who write the OS interfaces for their hardware. ... options active, prefast, PC-Lint, Coverity, and anything else you can find. ...
    (microsoft.public.development.device.drivers)
  • Re: using prefast throws an error
    ... I am using the DDKBUILD tool to do some driver development. ... you tried running prefast outside of my ddkbuild ... Mark Roddy DDK MVP ...
    (microsoft.public.development.device.drivers)
  • Re: PREfast suggestion!
    ... this would be rather simple for PREfast to catch as well. ... > Windows 2k/XP/2k3 Filesystem and Driver Consulting ... this was found on a single CPU machine. ... >> We try to also test on dual CPU, but I guess this build of our ...
    (microsoft.public.development.device.drivers)