Our website uses cookies to enhance your browsing experience.
Accept
to the top
>
>
>
V052. A critical error had occurred.
menu mobile close menu
Additional information
toggle menu Contents

V052. A critical error had occurred.

Jul 18 2017

The V052 message warns about a critical analyzer error. It is most likely that some source files will not be analyzed.

To get additional information about this error, examine the analyzer report file (plog) and the standard output stream of error messages (stderr), if you use the command-line version.

If you use the Visual Studio IDE or a standalone PVS-Studio application, the error stack is displayed in the PVS-Studio window. It is also recorded at the very beginning of the plog file. At the same time, the stack is divided into substrings, and each of them is recorded and displayed as an individual, unnumbered error.

If you work from the command line, you can analyze the return code of the command-line version to determine whether an exception occurred, and then examine the plog file without opening it in the Visual Studio IDE or the standalone application. For this purpose, the report can be converted—for example, into a text file—using the PlogConverter utility. Return codes of the command-line version are described in the section "Analyzing Visual Studio / MSBuild / .NET projects from the command line using PVS-Studio." Information about the PlogConverter utility can be found in the section "How to view and convert analyzer's results (SARIF, HTML, and other formats)."

Although V052 appears rather seldom, we would appreciate your help in identifying the issue that caused it. To do it, please send us the exception stack from the PVS-Studio output window, or the message from stderr if you use the command-line version, via the feedback form.