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.
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.

>
>
We Hit a Mark of 1000 Error Samples Col…

We Hit a Mark of 1000 Error Samples Collected from Open Source Apps!

Sept. 16, 2013
Author:

Our bug database where we collect samples of software errors detected in open source projects by our PVS-Studio static analyzer has recently reached the mark of 1000 samples!

It was some time ago that we decided to gather all the bugs found by PVS-Studio in open source applications in one place and made a single database. Although we go on with our usual task of writing and publishing articles to report checks (for example, Boost) and re-checks (for example, Chromium) of open source projects, we add every new defect we manage to find into this database. Sometimes the number of detected errors is not enough to write a good article, but they also get added into the database if we find them interesting.

What for do we maintain this bug database? First of all, it is a means of advertising our PVS-Studio code analyzer, of course. People won't read advertising posts which only abstractly praise the tool. One is always interested to know what particular errors it has found and in what particular real-life projects.

On the other hand, we believe that our bug database may serve as an excellent tutorial resource. Imagine you write a book or just an article explaining why it is bad to throw exceptions in C++ destructors. You naturally want to give real-life examples of errors related to this practice. And this is where our database comes in handy: you just open it and find there the diagnostic "V509. The 'throw' operator inside the destructor should be placed within the try..catch block. Raising exception inside the destructor is illegal." You can view the examples of bugs detected by the V509 diagnostic in projects like OGRE, TortoiseSVN and Chromium and cite them in your article, instead of abstract, artificial code samples. Or here's another situation. Imagine you are writing an article about sizeof(). No doubt, all the programmers ought to know the following rule: "The sizeof() operator returns size of the pointer, and not of the array, in given expression." But here we have error samples found by the V511 diagnostic in such projects as Wolfenstein 3D, Chromium, MySQL and Samba. These examples would well suit the demonstration purpose in your article.

Thus, our bug database is an excellent resource to aid preparing of articles and tutorials on C++. Authors are welcome to use it, which is absolutely free.

Popular related articles
The way static analyzers fight against false positives, and why they do it

Date: 03.20.2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
The Evil within the Comparison Functions

Date: 05.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…
The Ultimate Question of Programming, Refactoring, and Everything

Date: 04.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…
Appreciate Static Code Analysis!

Date: 10.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…
PVS-Studio for Java

Date: 01.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…
Free PVS-Studio for those who develops open source projects

Date: 12.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: 06.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…
The Last Line Effect

Date: 05.31.2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
PVS-Studio ROI

Date: 01.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…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: 07.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…

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