{"id":402509,"date":"2024-06-29T16:33:11","date_gmt":"2024-06-29T16:33:11","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=402509"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=402509","title":{"rendered":"Best warnings of static analyzer<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n

Everyone who runs the static analyzer on a project for the first time is slightly shocked by hundreds, thousands or even tens of thousands of warnings. It may be frustrating. Is my code so terrible? Or is the analyzer lying? In any case, filtering by the severity changes the situation, not completely though. That’s why we thought about how we could improve the first experience with the analyzer. Let me show you the new feature step by step…<\/p>\n

<\/figcaption><\/figure>\n

Intelligence Diagnostic Filter<\/h2>\n

What does a person, who runs code through a static analyzer for the first time, encounter? When run on large projects, a static analyzer produces a huge number of warnings for various code fragments.<\/p>\n

Yes, it may be an enormous number of warnings. Of course, there will be false positives<\/em> among them. Alas, static analysis cannot exist without false positives. Therefore, it was necessary to create a new approach that would simplify the process when one is just starting out with the analyzer.<\/p>\n

That’s how we got the idea to develop a special mechanism that would analyze a list of warnings and find the most interesting ones among them. We named it the Intelligence Diagnostic Filter<\/strong> or IDF<\/strong> for short.<\/p>\n

I will not go into the details of its implementation in this article. The developer<\/a> who created the mechanism will explain it better. So, don’t forget to subscribe to our Habr account<\/a> so as not to miss his article \ud83d\ude42<\/p>\n

Let’s look at the top ten warnings<\/h2>\n

Well, you have installed the analyzer<\/a> \u2013 what’s next? Of course, you need to run it on a large project<\/em>. Otherwise, the picture will be incomplete. There is a simple pattern<\/a> here \u2013 the more code lines<\/em> you have, the more difficult it is to maintain the code quality. Accordingly, the more difficult it is to maintain the code quality, the more bugs<\/em> this code contains.<\/p>\n

\"This
This is what the first run of the analyzer may look like…<\/figcaption><\/figure>\n

We have to admit, it’s not so exciting to appreciate the capabilities of the analyzer by looking through these warnings all at once. So open the additional toolbar and click on Best Warnings<\/em> button:<\/p>\n

\"Example
Example of the button in the PVS-Studio plugin for Visual Studio<\/figcaption><\/figure>\n

After a short processing pause, you get a list of the most significant code problems according to the IDF<\/strong>. This mechanism was also developed to demonstrate various features of the analyzer. Therefore, we limited the number of similar warnings in the output. This helps look at various types of code problems at once. This will also simplify further study of the remaining warnings.<\/p>\n

Note.<\/em><\/strong> Remember to mark the most interesting warnings with a star! It will be easier to find them later \ud83d\ude42<\/em><\/p>\n

What’s next?<\/h2>\n

Of course, do not ignore other warnings. The Analyzer Best Warnings<\/em> mode was made to help you see how PVS-Studio<\/strong> benefits your project. This mode also demonstrates the abilities of static analysis. Therefore, after studying the most significant code problems<\/strong> according to the IDF<\/strong> mechanism, let’s go back to other warnings.<\/p>\n

To do this, just click on the Best Warnings<\/em> button one more time:<\/p>\n

\"Example
Example of a button in the PVS-Studio plugin for Visual Studio<\/figcaption><\/figure>\n

Now it’s time to study all the remaining warnings. In fact, this is an optional step \u2013 you don’t have to view ALL the remaining warnings, you can view only High<\/em> level ones, for example:<\/p>\n

\"How
How to filter warnings in the PVS-Studio plugin for Visual Studio<\/figcaption><\/figure>\n

New warnings can get lost among the remaining ones. Also, the remaining warnings can distract you from the further use of the analyzer. In this case. So, I advise you to use the mechanism of warning suppression<\/a>.<\/p>\n

Click on the Suppress All Messages<\/em> button:<\/p>\n

\"How
How to suppress warnings in the Visual Studio plugin<\/figcaption><\/figure>\n

Now you will see the warnings strictly for the new code<\/em>. This is a super useful mechanism, so don’t be afraid to use it. You can always bring these warnings back to the log from the suppression file.<\/p>\n

Note.<\/em><\/strong> Warnings do not disappear without a trace! If you edit the code next to a suppressed warning, it will show up again.<\/em><\/p>\n

IDF development<\/h2>\n

Of course, we will further develop this intelligent filtering mechanism. Analyzer Best Warnings<\/em> is the first feature that is based on IDF<\/strong>, but it’s not the last one \ud83d\ude42<\/p>\n

We have various thoughts and ideas on how else we can use it. For example, we may add the ability to sort the entire report. This feature would be convenient, since later you can hide the least reliable warnings according to the IDF<\/strong>. Or we may add the ability to adjust the user-specific settings for projects…<\/p>\n

In a word, there are a huge number of ideas! However, the real driving force of changes and improvements is not developers, but users<\/em>. This is one of our most important principles \u2013 we take into account the wishes of our audience<\/em>.<\/p>\n

Try the new feature<\/a> and send us your thoughts and ideas! That way, we will not only find out what you think about the new mechanism, but also find the right vector of its development.<\/p>\n

Additional links<\/h2>\n