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.

OOO "Program Verification Systems&…

OOO "Program Verification Systems"'s plans on developing its own software products

Jun 09 2009

Since the beginning of the spring 2009 our company has been rapidly developing a new program product PVS-Studio which is a development of Viva64 and VivaMP code analyzers. Now it's high time it was announced. But before doing this I'll give a brief historical reference.

The first version of Viva64 1.0 software product was released December 31st, 2006 ( versions history). Of course its implementation was not at a high level for it was very important for us to launch the product as soon as possible and get users' response on the very technology of analyzing problems in 64-bit programs. And although it seems to me that we managed to avoid crude program errors, still even Viva64 2.0 version released July 9th, 2008 was far from being ideal.

Besides, November 27th, 2008 the first beta-version of our new VivaMP analyzer 1.00 beta was released which enabled the community of software developers to develop parallel programs in a simpler way with the help of OpenMP technology. The program was different from Viva64 only in the "stuffing", that is in the errors diagnosed, while VivaMP's interface was the same as in Viva64. Actually it was a copy of Viva64 operating in a different way. And although it is not convenient and logical from the user's viewpoint to have two identical programs (Viva64 and VivaMP), this approach allowed us to introduce the technology of detecting errors in parallel programs on market more quickly.

Now, in 2009 it's high time we improved our developments up to a more serious level.

I am glad to introduce a new software product by OOO "Program Verification Systems" named PVS-Studio (PVS is an abbreviation of our company's name). PVS-Studio is a static code analyzer intended for simplifying development of modern applications in C and C++ languages. PVS-Studio unites the preceding developments of the company (software products Viva64 and VivaMP) into one solution. Everything that has been performed by the two tools (Viva64 and VivaMP) before is now performed by one PVS-Studio tool.

At present PVS-Studio software product contains two code analyzers. The first one is intended for simplifying development of 64-bit applications and also reducing the cost of migration of obsolete 32-bit code on a new platform. Earlier this was a separate tool Viva64. The second code analyzer is intended for simplifying development of parallel programs using OpenMP technology. Earlier it was VivaMP product.

Thus, our two products Viva64 and VivaMP will be distributed as a single tool kit of code analysis tools under the name of PVS-Studio. Moreover, we have composed the PVS-Studio licensing conditions so that you can purchase both separate code analysis units and the whole tool at once. Licenses are intended for single developers and for teams of 1-5 persons.

PVS-Studio product differs from Viva64 and VivaMP in that it allows you to:

  • perform code analysis in several threads;
  • conveniently and quickly operate the filters of diagnostic messages and error codes;
  • launch analysis in batch mode (you need to prepare command files);

Release of PVS-Studio is planned by the end of the summer 2009. But as PVS-Studio is a logical development and continuation of the line of Viva64 and VivaMP products we have decided not to reset numbering of the product's versions. That's why the version to be released will have number 3.00. We are planning to stop releasing separate products Viva64 and VivaMP in future but they will be available as separate units in PVS-Studio.

I can define PVS-Studio software product as a code analyzer for solving modern problems which programmers face instead of detecting already known and irrelevant errors like uninitialized variables or access to a zero pointer which have become obsolete 10 years ago.

So we are planning to release PVS-Studio at the end of the summer 2009.

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