To get a trial key
fill out the form below
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

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

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

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

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.

How to work with the report of PVS-Stud…

How to work with the report of PVS-Studio in Linux

Oct 28 2016

I want to warn all the users of Linux-version of PVS-Studio 6.10.


WARNING! I want to point out that the log file, generated right after the analysis cannot be used! It serves as a source of data for the plog-converter program and is not intended for viewing.

We are getting a large number of letters from people, saying that it's impossible to use the results of PVS-Studio analysis. Programmers get a huge file with thousands of identical messages per one header *.h file and other rubbish. They start complaining. Some probably don't complain, but silently lose their interest for PVS-Studio.

These files weren't meant to be viewed. Plog-converter utility, which is described in the documentation was created to convert them into a "human" format. This utility doesn't only convert the log, but removes the duplicates for h-files, filters the messages and so on. For example, it is most useful to start viewing the report with the general analysis warnings of the first and second level (key -a GA:1,2). This is very important, because otherwise the programmer may simply drown in the huge "sea" of messages.

In the next version, we are planning to change the format of the initial log file, so that it is clear that it is some binary format and it is not meant to be viewed. This should give a hint to a programmer that he needs to do something with this file and after reading the documentation he will learn about plog-converter.

P.S. I will answer one question in advance: "Could you make your program in such a way that it issues a filtered report right away?"

Yes, we could, but there are two reasons not to do so.

1. Speed. Now during the parallel analysis every process appends to the end of the file. Thus the file is blocked only for a single-time record. That's quite fast and different analysis processes don't wait for each other. If we start filtering the duplicates for h-files, there will be a need to do the search along the file. This is much longer and the processes will start waiting for each other. There will be more downtime and the time of analysis will increase.

2. The full list of all the messages allows doing different selections without the need to restart the full analysis. I.e. if there is a situation when a person views the report and realizes that he doesn't want to see the diagnostics of the 3rd level. Then he edits the settings, starts plog-converter and has a new report in a minute. Otherwise, he will have to wait for an hour for the project to be analyzed once more.

Latest articles:


Popular related articles
PVS-Studio's data flow analysis untangles more and more related variables

Date: Aug 08 2022

Author: Artem Rovenskii

This is the second article about related variables and how the PVS-Studio analyzer deals with them. This time, let's talk about how we enhanced the mechanism we created, and what problems of the anal…
I want to use PVS-Studio in my project. The manager is against it. How to convince them?

Date: Aug 02 2022

Author: Sergey Vasiliev

You decided to integrate PVS-Studio into your project. But suddenly it turns out that the manager is against it, because... because why, actually? Let's try to figure out what to do with potential ob…
Intermodular analysis of C and C++ projects in detail. Part 2

Date: Jul 14 2022

Author: Oleg Lisiy

In part 1 we discussed the basics of C and C++ projects compiling. We also talked over linking and optimizations. In part 2 we are going to delve deeper into intermodular analysis and discuss its ano…
Intermodular analysis of C and C++ projects in detail. Part 1

Date: Jul 08 2022

Author: Oleg Lisiy

Starting from PVS-Studio 7.14, the C and C++ analyzer has been supporting intermodular analysis. In this two-part article, we'll describe how similar mechanisms are arranged in compilers and reveal s…
PVS-Studio evolution: data flow analysis for related variables

Date: Apr 28 2022

Author: Nikita Lipilin

Related variables are one of the main problems of static analysis. This article covers this topic and describes how PVS-Studio developers are fighting false positives caused by different relationship…

Comments (0)

Next comments
Unicorn with delicious cookie
Our website uses cookies to enhance your browsing experience.