To get a trial key
fill out the form below
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
RUB
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
** By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
** By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
** By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
>
How to not drown in the static analyzer…

How to not drown in the static analyzer's first report? [Mass Suppression]

Dec 15 2020

Have you ever used a statistical analysis tool on a new large project? If you have, you must know that the first scan may produce over 1 thousand and in some cases over 10 thousand warnings.

Luckily, you can control which warnings you want to work with. For example, you can limit the analysis to your project's newest code.

This video describes one of the ways to do so. We call this approach mass suppression, and it is especially helpful for large projects.

Comments (0)

Next comments
Unicorn with delicious cookie
Our website uses cookies to enhance your browsing experience. Would you like to learn more?
Accept