PVS-Studio 6.05 Site License
PVS-Studio 6.05 Site License | 44 Mb
The PVS-Studio tool is intended for developers of contemporary applications and it integrates into the Visual Studio 2015, 2013, 2012, 2010, 2008, 2005 environments providing the programmer with a convenient user interface to analyze files, navigate through code and get reference information. You do not need to study documentation and settings preliminarily to work with the analyzer. The analyzer is ready to work right after it is installed.
PVS-Studio Features
Integration with Visual Studio 2015, 2013, 2012, 2010, 2008, 2005;
incremental analysis is the automatic triggering of the analyzer at the moment immediately after compilation commences at developer's local system;
build-system independent file verification (through the compiler invocation monitoring system) by PVS-Studio Standalone;
online-help;
pdf-documentation;
saving and loading of analysis results;
capability of command line launch;
support of all cores and processors;
estimate of complexity of 64-bit code migration;
interactive filters;
convenient integration into the team development process;
marking of program text with the purpose of checking new code only.
PVS-Studio Advantages
Easy-to-download! You may download the PVS-Studio distribution package without registering and filling in any forms.
Easy-to-try! The PVS-Studio program is implemented as a plug-in for Visual Studio. The program is simple to install and does not require special setting before getting started.
Easy-to-buy! Unlike other code analyzers, we have simple pricing and licensing policy. We will not ask you what size your application's code is or thrust training courses on you by phone. You decide what you need on the order page, pay the purchase and get the registration key by e-mail.
Easy-to-support! It is the analyzer's developers who directly communicate with users, which enables you to quickly get answers to even complicated questions related to programming.
Supported languages and dialects
Visual Studio 2015 C, C++, C++11, C++/CLI, C++/CX (WinRT)
Visual Studio 2013 C, C++, C++11, C++/CLI, C++/CX (WinRT)
Visual Studio 2012 C, C++, C++11, C++/CLI, C++/CX (WinRT)
Visual Studio 2010 C, C++, C++/CLI, C++0x
Visual Studio 2008 C, C++, C++/CLI
Visual Studio 2005 C, C++, C++/CLI
MinGW C, C++, C++11
PVS-Studio is a static analyzer that detects errors in source code of C/C++ applications. There are sets of rules included into PVS-Studio:
General-purpose diagnosis
Detection of possible optimizations
Diagnosis of 64-bit errors (Viva64)
To learn more about each type of diagnosis, visit the corresponding pages.
The methodology of static code analysis we employ has significant advantages over other types of analysis since it allows you to cover the whole program code. The procedure of code check cannot damage the code itself in any way. The analysis process is completely controlled by person and it is the programmer who decides if it needs modification.
PVS-Studio 6.05
New PVS-Studio command line tool was added; it supports the check of vcxproj и csproj projects (C++ and C#). Now there is no need to use devenv.exe for nightly checks. More details about this tool can be found here.
The support of MSBuild plugin was stopped. Instead of it we suggest using a new PVS-Studio command line tool.
V755. Copying from unsafe data source. Buffer overflow is possible.
V756. The 'X' counter is not used inside a nested loop. Consider inspecting usage of 'Y' counter.
V757. It is possible that an incorrect variable is compared with null after type conversion using 'dynamic_cast'.
V3094. Possible exception when deserializing type. The Ctor(SerializationInfo, StreamingContext) constructor is missing.
V3095. The object was used before it was verified against null. Check lines: N1, N2.
V3096. Possible exception when serializing type. [Serializable] attribute is missing.
V3097. Possible exception: type marked by [Serializable] contains non-serializable members not marked by [NonSerialized].
V3098. The 'continue' operator will terminate 'do { ... } while (false)' loop because the condition is always false.
V3099. Not all the members of type are serialized inside 'GetObjectData' method.
V3100. Unhandled NullReferenceException is possible. Unhandled exceptions in destructor lead to termination of runtime.
V3101. Potential resurrection of 'this' object instance from destructor. Without re-registering for finalization, destructor will not be called a second time on resurrected object.
V3102. Suspicious access to element by a constant index inside a loop.
V3103. A private Ctor(SerializationInfo, StreamingContext) constructor in unsealed type will not be accessible when deserializing derived types.
V3104. 'GetObjectData' implementation in unsealed type is not virtual, incorrect serialization of derived type is possible.
New PVS-Studio command line tool was added; it supports the check of vcxproj и csproj projects (C++ and C#). Now there is no need to use devenv.exe for nightly checks. More details about this tool can be found here.
The support of MSBuild plugin was stopped. Instead of it we suggest using a new PVS-Studio command line tool.
V755. Copying from unsafe data source. Buffer overflow is possible.
V756. The 'X' counter is not used inside a nested loop. Consider inspecting usage of 'Y' counter.
V757. It is possible that an incorrect variable is compared with null after type conversion using 'dynamic_cast'.
V3094. Possible exception when deserializing type. The Ctor(SerializationInfo, StreamingContext) constructor is missing.
V3095. The object was used before it was verified against null. Check lines: N1, N2.
V3096. Possible exception when serializing type. [Serializable] attribute is missing.
V3097. Possible exception: type marked by [Serializable] contains non-serializable members not marked by [NonSerialized].
V3098. The 'continue' operator will terminate 'do { ... } while (false)' loop because the condition is always false.
V3099. Not all the members of type are serialized inside 'GetObjectData' method.
V3100. Unhandled NullReferenceException is possible. Unhandled exceptions in destructor lead to termination of runtime.
V3101. Potential resurrection of 'this' object instance from destructor. Without re-registering for finalization, destructor will not be called a second time on resurrected object.
V3102. Suspicious access to element by a constant index inside a loop.
V3103. A private Ctor(SerializationInfo, StreamingContext) constructor in unsealed type will not be accessible when deserializing derived types.
V3104. 'GetObjectData' implementation in unsealed type is not virtual, incorrect serialization of derived type is possible.
[/b]
[b]
Only for V.I.P Warning! You are not allowed to view this text.