To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* 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.

Useful Improvements in the PVS-Studio 6…

Useful Improvements in the PVS-Studio 6.17 Release

Aug 30 2017

Today we released a new version of PVS-Studio 6.17 static analyzer. In this version there are improvements, which, in my opinion, deserve a small note. I suggest to get acquainted with them, and then download the latest version of the distribution package.


We continue to develop our analyzer in relation to Linux. In other words, the Linux version is overtaking Windows version of analyzer on its abilities. The next step was the implementation of a plugin for SonarQube quality control system and adding a mode of mass warnings suppression for Linux. More detailed information can be received from the documentation sections "Integration of PVS-Studio analysis results into SonarQube" and "How to run PVS-Studio on Linux".

In the command line module PVS-Studio_Cmd.exe a new incremental analysis mode "AppendScan" was added. The usage of this mode will let "accumulate" information about the files that need to be analyzed. Thus, more options of performing the analysis become available that will let you configure the analyzer in terms of the needs of the project. More details are given in the article "PVS-Studio's incremental analysis mode".

Several new diagnostics were added, but nothing remarkable:

  • C++. V821. The variable can be constructed in a lower level scope.
  • C++. V1001. The variable is assigned but is not used until the end of the function.
  • C#. V3135. The initial value of the index in the nested loop equals 'i'. Consider using 'i + 1' instead.
  • C#. V3136. Constant expression in switch statement.
  • C#. V3137. The variable is assigned but is not used until the end of the function.

A much more interesting feature is that a mechanism of virtual values was significantly redesigned in the kernel of C++ analyzer. For example, now the analyzer performs a double loop passage, which allows it to define the range of possible values of variables, changing in a loop, more accurately. So don't be surprised if the analyzer starts issuing many warnings for that code which used to seem correct for the analyzer. We definitely recommend to upgrade the analyzer version because this way you will be able to find new bugs.

Another interesting improvement is the ability to make C++ analyzer think that malloc function cannot return NULL. Some programmers don't want to deal with the situation when the malloc returns a null pointer. That is why, pointers are used without prior check and, as a consequence, PVS-Studio analyzer issues plenty of warnings. Developers consider them as false positives and they asked for the ability to modify the behavior of the analyzer. An example of such an approach is described in the article "Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries". To configure the behavior of the analyzer special comments are used that are described in the section "Additional diagnostics configuration".

Also a plugin has been added in the distribution package which allows displaying analysis results in a Jenkins continuous integration system (so far available on Windows). This will allow you a better monitoring of the amount of potentially dangerous places in the project. A using the plugin for Jenkins is described in more detail in the article "Integrating PVS-Studio into the Continuous Integration Process" in the section "PVS-Studio plugin for Jenkins".

Other improvements:

  • The ability is also added to save reports of analyzer work from Visual Studio plugin and Standalone in txt\csv\html formats without a need to manually call PlogConverter.
  • License and file settings are now saved in UTF-8 encoding. For compatibility the analyzer supports files in UTF-16 format that we used previously.
  • A list of recently opened logs is added in a Visual Studio plugin menu.
  • Support of Visual Studio 2017 15.3 update.

Download and try the new version of the analyzer! Also, I'd like to take this opportunity to remind that we wrote a series of articles dedicated to a verification of a Tizen operating system code and hope they were interesting. If you missed the information about their publications, I suggest go over the links and get acquainted with these articles:

Popular related articles
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 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…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 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…
The Last Line Effect

Date: May 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…
Free PVS-Studio for those who develops open source projects

Date: Dec 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…
The way static analyzers fight against false positives, and why they do it

Date: Mar 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…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 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…
PVS-Studio for Java

Date: Jan 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…
PVS-Studio ROI

Date: Jan 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…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Evil within the Comparison Functions

Date: May 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…

Comments (0)

Next comments
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 →