How to Use Mass Suppression in PVS-Studio for C++?

Have you just run the analyzer and now you have no idea what to do with all this abundance of warnings? 📜 Nothing to worry about – we made a special mechanism that can help you deal with them 💪🏻

In this video, you’ll learn about the inner workings of mass warnings suppression mechanism in PVS-Studio for C++. If you’re interested in other programming language, follow the links bellow 🙂

Mass Suppression in PVS-Studio for C#

Mass Suppression in PVS-Studio for Java

Have fun watching this video and coding 🙂

Date processing attracts bugs or 77 defects in Qt 6

The recent Qt 6 release compelled us to recheck the framework with PVS-Studio. In this article, we reviewed various interesting errors we found, for example, those related to processing dates. The errors we discovered prove that developers can greatly benefit from regularly checking their projects with tools like PVS-Studio.

Continue reading

How to get nice error reports using SARIF in GitHub

Let’s say you use GitHub, write code, and do other fun stuff. You also use a static analyzer to enhance your work quality and optimize the timing. Once you come up with an idea – why not view the errors that the analyzer gave right in GitHub? Yeah, and also it would be great if it looked nice. So, what should you do? The answer is very simple. SARIF is right for you. This article will cover what SARIF is and how to set it up. Enjoy the reading!

Continue reading

MISRA C: struggle for code quality and security

A couple of years ago the PVS-Studio analyzer got its first diagnostic rules to check program code compliance with the MISRA C and MISRA C++ standards. We collected feedback and saw that our clients were interested in using the analyzer to check their projects for MISRA compliance. So, we decided to further develop the analyzer in this direction. The article covers the MISRA C/C++ standard and the MISRA Compliance report. It also shows what we already managed to do and what we plan to achieve by the end of the year.

Continue reading

Did it have to take so long to find a bug?

Have you ever wondered which type of project demonstrates higher code quality – open-source or proprietary? Our blog posts may seem to suggest that bugs tend to concentrate in open-source projects. But that’s not quite true. Bugs can be found in any project, no matter the manner of storage. As for the code quality, it tends to be higher in those projects where developers care about and work on it. In this small post, you will learn about a bug that took two years to fix, although it could have been done in just five minutes.

Continue reading

PVS-Studio 7.14: intermodular analysis in C++ and plugin for JetBrains CLion

The PVS-Studio team is increasing the number of diagnostics with each new release. Besides, we are improving the analyzer’s infrastructure. This time we added the plugin for JetBrains CLion. Moreover, we introduced intermodular analysis of C++ projects and speeded up the C# analyzer core.

Continue reading