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 →
PVS-Studio manual
- Introduction
- Analyzing projects
- Continuous use of the analyzer in software development
- Deploying the analyzer in cloud Continuous Integration services
- Managing analysis results
- Additional configuration and resolving issues
- Analyzer diagnostics
- Additional information
You can open full PVS-Studio documentation as single file. In addition, you can print it as .pdf with help virtual printer.
Introduction
- How to enter the PVS-Studio license and what's the next move
- PVS-Studio's trial mode
- System requirements
- Release history
- Release history for previous versions (before 7.00)
Analyzing projects
- Get started with PVS-Studio in Visual Studio
- Using PVS-Studio with JetBrains Rider and CLion
- Analyzing Visual Studio / MSBuild / .NET projects from the command line using PVS-Studio
- How to use PVS-Studio in Qt Creator
- How to run PVS-Studio Java
- PVS-Studio for embedded development
- How to use the OWASP diagnostic group in PVS-Studio
On Windows
- Getting acquainted with the PVS-Studio static code analyzer on Windows
- Compiler monitoring in PVS-Studio
- Direct integration of the analyzer into build automation systems (C/C++)
- Analysis of Unreal Engine projects
On Linux and macOS
- PVS-Studio C# installation on Linux and macOS
- Installing and updating PVS-Studio C++ on Linux
- Installing and updating PVS-Studio C++ on macOS
- How to run PVS-Studio C++ on Linux and macOS
Continuous use of the analyzer in software development
- Running PVS-Studio in Docker
- Running PVS-Studio in Jenkins
- Running PVS-Studio in TeamCity
- How to upload analysis results to Jira
- PVS-Studio and continuous integration
- PVS-Studio's incremental analysis mode
- Integration of PVS-Studio analysis results into SonarQube
- Unattended deployment of PVS-Studio
- Speeding up the analysis of C/C++ code through distributed build systems (IncrediBuild)
Deploying the analyzer in cloud Continuous Integration services
- Using with Travis CI
- Using with CircleCI
- Using with GitLab CI/CD
- Using with Azure DevOps
- Analyzing commits and pull requests
Managing analysis results
- How to display Best Warnings
- Baselining analysis results (suppressing warnings for existing code)
- Handling the diagnostic messages list in Visual Studio
- Suppression of false positive warnings
- Converting analysis results (PlogConverter tool)
- Relative paths in PVS-Studio log files
- Viewing analysis results with C and C++ Compiler Monitoring UI
- Notifying the developer teams (blame-notifier utility)
Additional configuration and resolving issues
- Tips on speeding up PVS-Studio
- PVS-Studio: troubleshooting
- Additional diagnostics configuration
- Predefined PVS_STUDIO macro
- PVS-Studio settings in Visual Studio / C and C++ compiler monitoring UI
Analyzer diagnostics
- PVS-Studio Messages
- General Analysis (C++)
- General Analysis (C#)
- General Analysis (Java)
- Diagnostics of micro-optimizations (C++)
- Diagnostics of 64-bit errors (C++)
- Customer's specific requests (C++)
- Problems related to code analyzer