PVS-Studio

PVS-Studio performs static code analysis and generates reports that help programmers find and fix bugs. PVS-Studio performs a variety of code checks, it is also useful for finding typos and copy and paste errors. Examples of such errors: V501, V517, V522, V523, V3001.

PVS-Studio 7 Patch is a tool for detecting bugs and security vulnerabilities in the source code of programs, which are written in C, C ++, C #, and Java. The analyzer can run overnight on the server and warn of suspicious code snippets. Ideally, these errors can be detected and corrected before they reach the repository. PVS-Studio Full Version can be started automatically immediately after the compiler for newly modified files.

PVS-Studio can be integrated into the Visual Studio 2010-2019 development environment. If you are using this IDE, you will probably just have to go to the PVS-Studio plugins menu and select “Check current projects”. However, this is often a more complicated process, so you will need to integrate PVS-Studio into an exotic building system. The subject of such integration is too broad to be explained here. You can find all the relevant information in our detailed documentation.

PVS-Studio 7 Key Features:

• Basic and consistent commitment to Visual Studio 2010-2017
• Scheduled investigation of regrouped individual records
• Online reference management for all diagnostics accessible in the program, on-site, and documents (displayed as a .pdf record) Up to 550 pages of documents
• Saving and stacking your inspection results allows for mid-term checks: in the middle of the night, the analyzer
• filters and gives you the results in the early part of the day you can save the research results in HTML format with the full source code path.
• Project research continues from the trend line: PVS-Studio 7.07.37949 coordinates the fracture in mid-range manufacturing operations; Another album will be released at the beginning of the day.
• Unusual diversity; support for multi-core frameworks and processors with the ability to indicate the number of cores to be used; IncrediBuild support.
• Intelligent separation of inspection results (registration document) in PVS-Studio 7.07.37949 Keygen window: by analytical number, registration name, and key phrase in the contents of the index.
• Scheduled check for updates (mid-range IDE and mid-range manufacturers).
• BlameNotifier tool. The device allows you to send email warnings to designers about errors that PVS-Studio Linux detected during nightly execution.
• Countless formats in projects created under Linux and macOS.
• Fingerprint as a false alarm: the ability to stamp a symbol to regulate a specific signal on a given symbol segment.
• Block Suppression – The ability to block all old messages sent to the inheritance code, with the goal of having the analyst report 0 alerts. You can usually go back to throttled messages later.
• This component allows you to seamlessly integrate PVS-Studio into your progress routines and highlight critical errors in new code as-is.
• Ability to see the speed of error correction, measure errors within a specific period of time, etc.
• Relative methods in document reporting to view on different devices.
• CLMonitoring allows you to highlight scans for tasks that do not contain Visual Studio documents (.sln / .vcxproj);
• In case the CLMonitoring utility is insufficient, there is a possibility that PVS-Studio will be formatted into a Makefile-based real model framework.
• Pvs-studio analyzer: a utility like CLMonitoring, but it works with Linux and macOS.

Supported languages ​​and compilers:

• The Windows. Visual Studio 2010-2017 C, C ++, C ++ / CLI, C ++ / CX (WinRT), C #
• Windows IAR Embedded Workbench, C / C ++ compiler for ARM C, C ++
• Windows Keil µVision, DS-MDK, ARM 5/6 C compiler, C ++
• Windows Texas Instruments Code Composer Studio, ARM C, C ++ code generation tools
• Windows toolchain GNU Arm Embedded, GCC Arm Embedded compiler, C, C ++
• Windows Clang C, C ++
• Windows MinGW C, C ++
• Windows Java

How does PVS-Studio 7.13.48133 Work?

• The abstract syntax tree-based model-based analysis looks for fragments in the source code that are similar to known code models with errors.
• Method annotations provide more information about the method used than those obtained by scanning only signatures.
• Data flow analysis (data-flow analysis) is used to evaluate the limits placed on the values ​​of variables when processing various language constructs. For example, analyzing the flow of data makes it possible to evaluate the value that a variable can take in a blocked if / else.
• The program’s semantic model-based inference type provides the parser with complete information about all variables and instructions in the code.
• Symbolic execution evaluates the value of a variable that could be causing an error, by performing a range check.
• Polluted data analysis (polluted data analysis) detects cases where the application uses unverified user data. Too much trust in this data can lead to vulnerabilities (eg SQLI, XSS, traverse paths).

What’s new in PVS-Studio?

• PVS-Studio C# analyzer can now analyze projects for .NET 5 platform.
• A new diagnostic rule for OWASP ASVS standard, which was added in this release to PVS-Studio C# analyzer, can find SQL Injection tainted data patterns (the rule V5608). The tainted data category of potential security vulnerabilities holds an important position in OWASP’s Top 10 rating. In future releases, we plan to expand PVS-Studio capabilities to include the detection of more tainted data patterns.
• The Blame Notifier automatic analysis report generation and notification tool now support sorting analyzer messages by commit numbers and dates based on blame information retrieved from the version control system. This allows you to identify analyzer warnings that appeared on a particular day.
• Continuing on the topic of automatic publication of analyzer reports – it is now possible to accomplish this without using our Blame Notifier tool. One of our users created a lightweight alternative (which does not depend upon . NET) which you can find on GitHub.
• Support for analyzing Ninja projects under Windows though JSON Compilation Database (compile_commands.json) was improved for PVS-Studio C++ analyzer.
• By using clang to build a PVS-Studio C++ analyzer we’ve achieved an overall improvement in analyzer’s performance up to 10% when analyzing source files on Windows operating system.
• PVS-Studio JetBrains Rider plug-in now supports Rider 2021.1.
• File with suppressed analyzer messages can now be specified directly through the command line for PVS-
• Studio_Cmd.exe, a tool for analyzing C++ and C# Visual Studio projects. Previous analyzer versions could only read suppression files through the project or solution.
• V832. It’s better to use ‘= default;’ syntax instead of the empty body.
• V1070. The signed value is converted to an unsigned one with subsequent expansion to a larger type in the ternary operator.
• V1071. Consider inspecting the foo function. The return value is not always used.
• V1072. The buffer is securely cleared not on all execution paths.
• V1073. Consider checking for misprints. Check the following code block after the ‘if’ statement.
• V2577. MISRA. The function argument corresponding to a parameter declared to have an array type should have an appropriate number of elements.
• V2578. MISRA. An identifier with array type passed as a function argument should not decay to a pointer.
• V2579. MISRA. The macro should not be defined with the same name as a keyword.
• V2580. MISRA. The ‘restrict’ specifier should not be used.
• V2581. MISRA. Single-line comments should not end with a continuation token.
• V2582. MISRA. Block of memory should only be freed if it was allocated by a Standard Library function.
• V3170. Both operands of the ‘??’ operator are identical.
• V3171. A potentially negative value is used as the size of an array.
• V3551. AUTOSAR. An identifier with array type passed as a function argument should not decay to a pointer.
• V5013. OWASP. Storing credentials inside source code can lead to security issues.
• V5608. OWASP. Possible SQL injection. Potentially tainted data is used to create SQL commands.

What’s New In PVS-Studio?

• Improvement in analyzer’s performance
• New mapping for its diagnostic rules
• Static Application Security Testing (SAST)
• Fixes safety flaws and vulnerabilities
• Other bug fixes and improvements.

System Requirements

• Operating System: Windows Vista/ 7/ 8/ 8.1/ 10 or Server 2008/ 2012/ 2016/ 2019 (32-bit or 64-bit – all editions)
• Processor: 3.0 GHz or faster
• RAM: 2 GB
• Free Hard Disk Space: 500 MB
• Microsoft .NET Framework 4.7.2
• Visual Studio 2010-2022

Download PVS-Studio