Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

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

close form
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

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

close form
check circle
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" announces the issue of a new version of the static code analyzer - Viva64 2.30

Apr 20 2009
Author:

OOO "Program Verification Systems" announces the issue of a new version of the static code analyzer - Viva64 2.30. Viva64 tool is designed for searching errors in the code of 64-bit applications and for their performance increase.

Now the code analyzer will help the developers in optimizing the size of RAM used by the program. In the new version, a new diagnostic message V401 has been added, it lets find data structures which use memory uneconomically.

Constants processing has been improved, in a number of cases this reduces the quantity of false diagnostic warnings. The mechanism which hides double errors in header files indicated in relative views has been enhanced. Before that, during a project testing, the error in #include "lib\file.h" and #include "lib\..\lib\file.h" would be considered as if located in different files. Two diagnostic warnings would be given. Now paths are exposed, and the analyzer does not indicate twice the errors contained in the file "file.h".

Popular related articles
PVS-Studio 7.26: running analysis in VS Code and Qt Creator, integration with DefectDojo, and more

Date: Aug 17 2023

Author: Sergey Vasiliev

PVS-Studio 7.26 has been released. Now you can run the analysis in plugins for VS Code and Qt Creator; upload the analysis results to DefectDojo, and more. In this note, we'll take a closer look at...
PVS-Studio 7.25: support for latest versions of Qt Creator, Rider, and more

Date: Jun 15 2023

Author: Nikita Lipilin

PVS-Studio 7.25 has been released. In this version, we implemented the support of Qt Creator 10 and Rider 2022.2.3 (and higher), updated the libraries used by the analyzer, enhanced the documentation…
PVS-Studio 7.24: Unity, advanced warning suppression and much more

Date: Apr 13 2023

Author: Nikita Lipilin

PVS-Studio 7.24 is released. We enhanced the analysis of Unity projects, introduced new features for handling suppress files (*.suppress), implemented new diagnostic rules, and so on. Learn more...
PVS-Studio 7.23: Qt Creator 9 plugin, and more

Date: Feb 16 2023

Author: Nikita Lipilin

PVS-Studio 7.23 is released. We improved the Qt Creator support, increased the stability of PVS-Studio Java, solved issues with the analysis of NMake projects, added a number of new diagnostics, and.…
PVS-Studio 7.22: Visual Studio Code, Qt Creator, .NET 7

Date: Dec 16 2022

Author: Sergey Vasiliev

PVS-Studio 7.22 has been released. It includes plugins for Visual Studio Code and Qt Creator, support of .NET 7 projects analysis, enhanced Best Warnings filter and new diagnostic rules. Learn more...


Comments (0)

Next comments next comments
close comment form