To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Unable to analyze a file with 'import' …

Unable to analyze a file with 'import' directive (compiler internal error 'msc1.cpp'). What shall I do?

Feb. 28, 2019

Several times, we got complaints from users that the analysis of some parts of projects wasn't working any more. A common twist was the usage of the '#import' directive in problematic files. This note will briefly describe the reasons of the problem and what has to be done to resume the analysis.

Note. This note is relevant only for Windows when using the 'cl.exe' compiler for preprocessing.

Problem

PVS-Studio uses preprocessed files to search for bugs in code written in C, C++. To get them, the analyzer relies on third-party tools, including the cl.exe compiler. The '/P' flag is used to tell cl.exe to generate preprocessed files.

The problem is that starting from the Visual Studio 15.8 version (and the corresponding Visual C++ version - VC++ 2017 version 15.8 v14.15 toolset), when running cl.exe with the '/P' flag on the files, containing the '#import' directive, an error occurs in the compiler.

Nevertheless, when a compiler is not passed the '/P' flag, a build is performed successfully. From the outside, it might look something like this: a project is successfully built, but the PVS-Studio analyzer does not work. On problem files, the analyzer output will look like this:

c:\program files (x86)\microsoft visual 
studio\2017\community\vc\tools\msvc\14.16.27023\include\comdef.h: 
fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1518)
Internal Compiler Error in c:\program files (x86)\microsoft visual 
studio\2017\community\vc\tools\msvc\14.16.27023\bin\hostx64\x64\cl.exe

If you faced such a problem, most likely, your project uses the Platform Toolset V141 and the problem occurred after updating Visual Studio and Visual C++ related packages (and, accordingly the compiler) to a newer version. As a result, the project build is still going successfully, but the analysis - isn't.

To make sure that the problem owns to the compiler, you can try setting the '/P' flag in the configuration options of the related project and perform the build. Setting the flag: Properties|C/C++|Preprocessor|Preprocess to a File -> Yes(/P).

By the way, there is a special topic on the Visual Studio forum: https://developercommunity.visualstudio.com/content/problem/313306/vs2017-158-internal-compiler-error-msc1cpp-line-15-1.html

Solutions

Unfortunately, the described problem still exists and will be fixed, most likely, only in the next Visual Studio release. However, you can continue using PVS-Studio for checking projects, affected by this problem, using a small workaround.

Usage of the 'PVS_STUDIO' macro

When the analyzer runs the compiler in the preprocessing mode, an additional macro is specified - 'PVS_STUDIO'. By using this macro, you can wrap the problematic lines by the #ifdef directive - this will enable the preprocessor to ignore them, without affecting code compilation. At least, you should wrap the '#import' directive:

#if !defined(PVS_STUDIO)
 #import
 ...
#endif

Note, that in this case the part of code, wrapped in the directive, won't get in the resulting preprocessed files. In most cases, this edit won't affect the analysis results.

Usage of the working compiler version

Note. This problem was solved in the compiler version as part of Visual Studio (2017) 15.9.14.

You can opt to use an earlier compiler version (or a new fixed one), in which there is no problem, described above. Let me note, that it appeared starting from the VC++ 2017 Version 15.8 v14.15 toolset.

Note, that Visual Studio 2017 allows installing several Platform Toolset V141 instances on this system, which will get you out of the need to roll back the Platform Toolset version in the project.

0613_ImportCompilerInternalError/image1.png

You can specify the desired compiler versions in the files <VsInstanceDir>\VC\Auxiliary\Build\Microsoft.VCToolsVersion.default.[txt|props], where <VsInstanceDir> - configuration directory of a specific Visual Studio release.

Popular related articles
Free PVS-Studio for those who develops open source projects

Date: 12.22.2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: 10.22.2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
The Ultimate Question of Programming, Refactoring, and Everything

Date: 04.14.2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: 11.21.2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
PVS-Studio ROI

Date: 01.30.2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: 07.31.2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The Last Line Effect

Date: 05.31.2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
The Evil within the Comparison Functions

Date: 05.19.2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
PVS-Studio for Java

Date: 01.17.2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
The way static analyzers fight against false positives, and why they do it

Date: 03.20.2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept