To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.

>
>
>
Static Code Analyzer Issues No Warnings…

Static Code Analyzer Issues No Warnings (False-Negative Results)

Jul 07 2021

Tools that perform static code analysis may not detect errors for the following main reasons:

  • A high-level error that can't be detected at the source code analysis level.
  • Developers do not know about an error pattern or have not implemented its search in the analyzer.
  • Some algorithms have flaws and fail to search for errors.

Let's look into these reasons in a little more detail. Interested to learn how static code analyzers work in general? Be sure to check out the article: "Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities".

High-Level Errors

Let's say technical requirement said that a specific value had to be calculated by the formula "cos(x) / 2". When implementing algorithms, the developer mistyped and wrote sin instead of cos in the program code:

y = sin(x) / 2;

Such program code makes it impossible to find an error like this. Only much knowledge about the program itself may help—just the code fragment is of little use. Static analysis will not work out in this case.

No Such Diagnostic in the Analyzer

One can make a mistake in a great variety of ways. Still the situation is not as desperate as it appears. Typically, programmers' mistakes fit some patterns that you can notice and point out. Such cases serve as a basis for diagnostics that will detect many of such errors. In other words, certain error patterns become notable. Examples include null pointer dereference, buffer overflow, resource leak, and others.

There will always be exotic bugs that none of the existing code analyzers can uncover. There's no need to worry about this. After all, developers should focus primarily on identifying common error patterns. Next, developers should learn to search for little less frequent cases. Thus, developing any static analyzer is an infinite process of approaching an unattainable ideal. Some analyzers have advanced more, some less.

The PVS-Studio team draws inspiration to implement new diagnostics from the following sources:

  • Our own experience.
  • Books, articles, talks.
  • User feedback. By the way, if you have an idea for a new diagnostic, we'll be happy if you share it with us.
  • Chats on websites, like StackOverflow.
  • And others. Interesting example.

Machine learnings is one of the ways to get around manual writing diagnostic rules. The main idea is to teach the analyzer to find errors itself by learning on a large base of open source code. Unfortunately, our team is quite skeptical about this topic. We set out our vision in the article "Machine Learning in Static Analysis of Program Source Code".

Implementation Drawbacks

Diagnostics' implementation may let slip special cases. You can always write code so that an error will hide from the analyzer.

Besides, diagnostics are tied to other analyzer mechanisms. These mechanisms, such as data flow analysis, have limitations too. For example, we're constantly improving data flow analysis in PVS-Studio, but it's an endless process. What's more, some cases are algorithmically intractable.

Additional links:

Popular related articles
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 →
Accept