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.

Viva64: What Is It, and Who Is It for?

Viva64: What Is It, and Who Is It for?

Jul 30 2007

Viva64 is a tool designed for software developers. With this tool, you can easily convert 32-bit applications to 64-bit ones.

At present, Viva64 and VivaMP software products are included in PVS-Studio as parts of it and are no longer distributed as separate applications. Please use PVS-Studio program to obtain the necessary possibilities of code verification.

A problem of the nearest future: release of 64-bit applications

Personal computers with 64-bit processors appeared on the market only at the beginning of 2006. Right after that, developers began to modify their applications to make them compatible with the new architecture. However, it suddenly turned out that applications could work incorrectly when running on new platforms. Standard means of diagnostics do not allow determining the new class of errors that occur in applications, and it is not good to leave those errors unfixed either.

The necessity to convert applications to 64-bit ones placed developers in a difficult situation. The behavior of applications that have worked for years without any problems has become unpredictable. Of course, there is more random access memory for applications, however, when working with greater amounts of data applications may hang, crash, or even they may generate useless files instead of the needed results.

Viva64 is a solution to the problem

One of possible solutions that can be used to search for errors when converting code is the use of special tools - static code analyzers. Viva64 is one of such tools. It is a code analyzer that finds potential errors in applications written in C and C++.

Viva64 is integrated into Microsoft Visual Studio 2005 as its extension module. Below is the appearance of Microsoft Visual Studio 2005 with Viva64 integrated into it.


Figure 1. The appearance of Microsoft Visual Studio 2005 with Viva64 integrated into it.

This allows developers to work with Viva64 in a familiar environment - there is no need to spend time on familiarizing with a new interface. Viva64 just adds a few new elements (in Fig.1 they are marked with red): the Viva64 menu item, a toolbar containing Viva64 commands and a window containing the list of found problems. Any developer can easily figure out how to work with Viva64.

Figure 2 demonstrates an example of Viva64 documentation. This is a description of one of the errors found by the code analyzer. The description is in the format that is compatible with the standard MSDN help system, and it can be automatically integrated into it. So, developers will not have to familiarize themselves with a new help system.


Figure 2 - A description of an error found by Viva64.

Viva64 allows you to:

  • find incorrect constructions in code (from the point of view of 64-bit applications);
  • make a precise and complete diagnostic of errors, right up to the line number and error description;
  • navigate to incorrect code snippets;
  • analyze the aftermath an error may cause. This is done with the help of detailed documentation that is integrated into the MSDN help system;
  • find ways to fix problems by using examples the documentation contains;
  • analyze the code of the entire project or solution (in Microsoft Visual Studio terminology), but not only single files.

Viva64 and competitors' products

I'd like to name the main competitors of Viva64, as well as similar means of analysis.

First of all, I'd like to note that Microsoft Visual Studio 2005 already includes a primitive tool that searches for possible conversion problems. However, this tool is not a Viva64 competitor, since it provides only preliminary code analysis. Viva64 provides a much higher level of code analysis and diagnostics.

Below is a list of tools that are similar to Viva64:

The above-mention products are code analyzers as well. Here is what makes Viva64 different:

  • Viva64 searches only for those errors that occur during code conversion. The competitive tools are general-purpose code analyzers. Though it is announced that the competitive tools can search for conversion problems, it's actually hard to use them to analyze Windows applications. The point is that they are mainly intended for Unix applications.
  • Viva64 is completely integrated into Microsoft Visual Studio, which makes it possible to navigate to files, projects and solutions, jump to problematic code snippets and use the integrated help system.
  • Since Viva64 is used only for one purpose (it searches only for conversion errors) it's very easy to customize it. Viva64 is ready to function right after it is installed, which is a real advantage that the competitive products do not have.


In general, I can say that the use of Viva64 will allow you to greatly reduce the time needed to prepare 64-bit applications for the release. This happens because potentially dangerous code snippets are found automatically - there is no need to spend a lot of time searching for them manually.

Also, Viva64 brings your applications to a higher quality level. It's quite possible that developers can miss some errors when analyzing code manually. Viva64 allows you to avoid this.

Popular related articles
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…
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…
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…
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…
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…
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…
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…
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 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…

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 →