PVS-Studio Static Code Analyzer for 64-bit and parallel C/C++ code
Our Customers
|
PVS-Studio code analyzer is based on VivaCore Library
|
|
28.06.2010
Why is the number of the line where an issue was found sometimes absent in the Error List in PVS-Studio?
Sometimes the PVS-Studio code analyzer seems to find an issue in the code on which it generates a message, specifies the file name but does not show the number of the line with the issue as shown in the figure.»
Sometimes the PVS-Studio code analyzer seems to find an issue in the code on which it generates a message, specifies the file name but does not show the number of the line with the issue as shown in the figure.»
07.06.2010
Communication between developers and users
Abstract When developing software products, developers need very much to get feedback from users of their programs.»
Abstract When developing software products, developers need very much to get feedback from users of their programs.»
22.07.2010
Using PVS-Studio with continuous integration systems
This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
06.07.2010
Comparing capabilities of PVS-Studio and Visual Studio 2010 in detecting defects in 64-bit programs
In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
29.06.2010
A Collection of Examples of 64-bit Errors in Real Programs
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.»
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.»
22.07.2010
We released a new version of PVS-Studio code analyzer - PVS-Studio 3.61»
10.06.2010
We released a new version of PVS-Studio code analyzer - PVS-Studio 3.60. »
19.05.2010
Our workers visited the GDC2010 conference that was held on May, 14-16, 2010, in Moscow and talked to many developers who participated there.»
Terminology
Win32
The term Win32 is used in various contexts.
By Win32 a family of 32-bit Windows operating systems for the architecture x86 is understood.
When one speaks about a Win32-application, you should understand that one means a 32-bit program to be executed in the 32-bit environment and that has the ILP32data model.
By Win32 a 32-bit API is also understood which is provided by the 32-bit Windows operating system.
There is a subsystem WoW64 on new 64-bit Windows systems to provide compatibility with obsolete 32-bit applications. The system translates the calls of the 32-bit API into the calls of the 64-bit API, redirects requests when working with the register and files and performs some other functions.
References
- Wikipedia. Windows API.
- Migrate Using Win32/Win64. Chapter 1: Introduction to Win32/Win64.