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.
As a PVS-Studio's developer, I am often asked to implement various new diagnostics in our tool. Many of these requests are based on users' experience of working with dynamic code analyzers, for example Valgrind. Unfortunately, it is usually impossible or hardly possible for us to implement such diagnostics. In this article, I'm going to explain briefly why static code analyzers ...