Download as PDF, PPTX
Uploaded byAndrey Karpov
PVS-Studio in 2021 - Feature Overview
PVS-Studio 7.12 offers 905 diagnostics for C++, 171 for C#, and 106 for Java, focusing on code quality, security, and safety. It enhances debugging by detecting a variety of issues, such as memory access errors and security vulnerabilities, making it suitable for developers, managers, and security professionals. The tool provides multiple analysis options, including local, incremental, server-side, and cloud analysis, to integrate seamlessly into development workflows.
More Related Content
Similar to PVS-Studio in 2021 - Feature Overview
PVS-Studio in 2021 - Feature Overview
- 1. PVS-Studio in 2021 FeatureOverview russian version
- 2. PVS-Studio 7.12 905 Diagnostics guardsquality, security (SAST), and code safety 13 years on the market 2 🔍 404 for C++ 🔍 171 for C# 🔍 106 for Java 🔍 … и 224 specific ones
- 3.
- 4. When should youstart using PVS-Studio?
- 5. For a developer🔥 You make occasional mistakes during development 🔥 Debugging when searching for errors is time consuming 🔥 Errors get into the version control system 🔥 Once an error is found by QA specialists, it’s diicult to debug that code 5
- 6. For a manager💡 You frequently return to old tasks due to bugs 💡 Users report errors in your products 💡 You hire more developers but notice a decline in code quality 💡 With the increasing amount of code, it becomes diicult to assess its quality and reliability 6
- 7. For a security professional 🔒You experience diiculties with external code audit 🔒 Clients require to use security and safety standards in development 🔒 Potential customers require the use of such tools 7
- 8. What can PVS-Studiodetect?
- 9. memory access errors typos array index outof bounds buer overflow incorrect method handling serialization / deserialization errors unreachable code security issues and much more... incorrect type handling synchronization errors Types of problems 9
- 10.
- 11. Generate reports Plog Converter component Generatereports in a convenient format to integrate into your backend processes 11
- 12. Distribute results Blame Notifier component Sendanalysis results to commit authors to keep your code base clean 12
- 13. What about analysisoptions?
- 14. Local analysis Basic usemodel, runs on developers’ computers 14
- 15. Incremental analysis Check only changedcode with this mode - save time for more important tasks 15
- 16. Server-side analysis Integrate PVS-Studio intonightly builds - every morning you’ll get a detailed report about the code base state 16
- 17. Cloud analysis Run analysison continuous integration services in addition to your company infrastructure tools 17
- 18. Pull-request analysis Check individual commitsand entire pull-requests to simplify code review 18
- 19. IDE and developmenttools
- 20. Filter by certaintylevel Fragment with an error Mark as False Alarm 20
- 21. Code quality IDE Visual Studio IntelliJIDEA Rider CLion Qt Creator Eclipse Game engines Build systems MSBuild CMake Make Ninja Gradle Maven Unreal Engine Unity SonarQube 21
- 22. CI Embedded Keil µVision, DS-MDK IAREmbedded Workbench Platform.io QNX Momentics TI ARM Code Generation Virtualization Docker WSL Cloud CI CircleCI Travis CI GitLab Azure DevOps Jenkins TeamCity 22 Distributed build IncrediBuild
- 23. What about legacycode?
- 24. Don’t waste time digginginto warnings after the first run
- 25. Focus on issues innew code
- 26. Add all warningsto the suppress file More about mass suppression... 26
- 27.
- 28. Interested? try PVS-Studio forfree 🔗 Download PVS-Studio 🔗 Request a trial 🔗 Enter a license What’s next?