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

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* 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.

>
>
The new version of the PVS-Studio 4.00 …

The new version of the PVS-Studio 4.00 BETA analyzer is ready

Nov 24 2010
Author:

We are glad to announce the release of the new version of the PVS-Studio 4.00 static code analyzer that is now intended not only for 64-bit and parallel software developers but for a wider range of programmers as well. We say so because the new version of our tool includes a FREE general-purpose analyzer. Analysis of parallel software is also free now and only analysis of 64-bit software remains paid. That is what the changes in the licensing policy is concerned. Besides, we created a new window for displaying diagnostic messages (it has become much more convenient) and made the tool much faster.

Brief information about the product and PVS-Studio 4.00 version

Beginning with version 4.00, PVS-Studio includes three sets of rules:

  • a set to detect migration issues and develop new 64-bit software from scratch (Viva64);
  • a set to develop parallel OpenMP software (VivaMP);
  • a new set of general-purpose rules for general software analysis.

The analyzer handles code of software written in C and C++.

PVS-Studio is shipped as a plugin for the Microsoft Visual Studio 2005/2008/2010 development environment.

Out of the three rule sets available in PVS-Studio (64-bit, OpenMP and general analysis), only the 64-bit software analysis is a paid solution (you may get a 30-day trial version that displays only a part of issues found in your code). The other two rule sets – analysis of OpenMP-issues and general analysis – are free.

You may download PVS-Studio here: /en/pvs-studio/download/

Detailed description of new features in PVS-Studio 4.00

A new set of general-purpose static analysis rules

We have developed a new set of general-purpose static analysis rules. By the moment of release of version 4.00, it includes more than forty rules that let you find issues in code of general character.

When we were starting to develop a general-purpose static analyzer, we did not intend to copy rules from already existing tools. We rather concentrated on creating contemporary rules some of which were absolutely our own ideas. We consciously refused to implement obsolete diagnoses available in any similar tool with a ten-year history. So, we include only new and relevant rules into our tool.

Release of version 4.00 with a set of more than forty rules is only the first step. We intend to implement much more diagnostic rules in future.

Here is also important and nice news: this set of rules is absolutely free, you may use it both for private and commercial purposes, at home or in your office. Perhaps we will make this rule set paid in time as it becomes much larger, but we are not planning it now.

Changes in the licensing policy

The pricing policy for PVS-Studio 4.00 underwent significant changes. While there were only two analyzers (to detect 64-bit and parallel issues) and all the sets of analysis rules were paid, now we have changed this. So, now you must pay only for the rule set intended for usage while porting and developing new 64-bit code (Viva64). The other two rule sets – analysis of OpenMP-issues and general analysis – are free and can be used both for commercial and non-commercial purposes at home and in office.

Thus, users have to purchase only 64-bit diagnosis (Viva64) if they need it.

There are still three types of licenses available: Single User License, Team License, Site License.

Users that purchased the license for PVS-Studio not earlier than a year ago may automatically update the old version up to version 4.00 for free – your old registration keys will remain valid. Those users who purchased the license earlier than a year ago may update their version up to version 4.00 too but they will not be able to use some new diagnostic rules in the 64-bit analysis. To get a complete version, these users will have to renew the license for 80% of its initial price.

To learn more about prices and licensing policy, visit this page: /en/order/

A new window for diagnostic messages generated by the analyzer

We used standard Visual Studio windows to display diagnostic messages until the release of PVS-Studio 4.00 – these are Output Window and Error List. This method had a lot of disadvantages: we could not provide convenient handling of our tool because we could not extend standard Visual Studio elements. That is why we developed our own window to display diagnostic messages. This allowed us to make the tool more convenient for our users. We intend to significantly extend this functionality in future making usage of PVS-Studio more convenient.

Speed increase

The process of static code analysis is slower than, for instance, the compilation process. It is determined by the fact that the analyzer performs much more work to gather and process information about application's code. That is why our constant priority task is to increase the speed of our tool. There are two methods to achieve it and we use both of them. First, we regularly improve analysis procedures to make it faster. Second, the new window for displaying diagnostic messages let us significantly improve inner data representation structures, which made handling of the message list faster.

Information about company

OOO "Program Verification Systems", Russian company (the city of Tula) founded in 2008. The main product developed by the company is the PVS-Studio static code analyzer.

Product's page: /en/pvs-studio/

Prices and types of licenses: /en/order/

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…
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…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
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 Ultimate Question of Programming, Refactoring, and Everything

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

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 →
Accept