Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
Message submitted.

Your message has been sent. We will email you at


If you do not see the email in your inbox, please check if it is filtered to one of the following folders:

  • Promotion
  • Updates
  • Spam

>
>
Possible issues relating to stdafx.h wh…

Possible issues relating to stdafx.h when using PVS-Studio

Sep 15 2009
Author:

Sometimes, when testing the code of applications with the help of PVS-Studio, you may face some problems with stdafx.h file which is a part of the mechanism "precompiled headers". For example, PVS-Studio can warn that this file cannot be found. Or, if there are several stdafx.h files, the wrong one will be used. But no problems occur during compilation in Visual C++.

This situation is not an error from the viewpoint of PVS-Studio. The point is that stdafx.h is processed in Visual C++ in a special way. Sometimes some of the exceptions from the rules of file processing apply to it. Simply speaking, Visual C++ processes stdafx.h file not like all the other header files.

There is no such special processing of stdafx.h in PVS-Studio analyzer (as well as in many other similar tools). That's why when testing the code with the help of PVS-Studio you can sometimes see errors relating to stdafx.h.

To avoid the errors, stdafx.h file must be processed in the same way as all the other header files. You do not need to disable "precompiled headers" for that. But disabling "precompiled headers" can help you detect errors in the organization of the project's files.

So, if you have problems with stdafx.h file when testing code with the help of PVS-Studio, although these problems do not occur when compiling the code, you can do the following.

  • Make sure that the whole code is correctly compiled (completely). To do so use "Rebuild Solution" command.
  • Disable "precompiled headers" for the project. If the project's files are organized correctly the project must still be able to compile. If there are compilation errors occurring with "precompiled headers" disabled, correct them.
  • Enable "precompiled headers".
  • The project is ready for testing with PVS-Studio.
  • I should note that these actions are necessary only in that case if there are errors relating to stdafx.h file when testing code with the help of PVS-Studio. But if the project's files are organized correctly, PVS-Studio can work with "precompiled headers" very well.
Popular related articles


Comments (0)

Next comments next comments
close comment form