Bugs. Bugs never change

You have opened an article to which you must link to Twitter. Or place it in your favorite programmer group. This will benefit both us and open projects. So that programmers from all over the world know about PVS-Studio, we check open projects and make them better. And at the same time we write interesting and useful articles. The more people learn about our articles, the more pleasant we will do it and the more projects we will check. Joint profit.

The idea of ​​checking open projects to promote their products is not new. However, we do what no one else does. We describe in detail the results of our checks.

You can often see notes about project validation using a static analyzer X. However, these are either common words or a mixture of analyzer messages and diff results. Empty advertising is not interesting to read. And from the report on the changes in the code, it is difficult for an uninitiated person to understand what the essence of the error is.

We are not lazy. We try to describe in detail what the essence of the error is, how to correct it and how to avoid such errors as far as possible. Here are the results of our many years of work:
')
An updated list of articles in which we talk about errors found with PVS-Studio in open source projects.

Reading our articles is not only interesting, but also useful. Even experienced programmers will learn from them about new error patterns and dark corners of C ++.

To make it interesting, we give preference to well-known programs. For example, you can get acquainted with errors in the code of the following projects:

• CoreCLR
• Libreoffice
• Qt
• Clang
• Chromium

We do not write articles about all proven projects. Some of the projects are too small or contain few interesting bugs. However, we will certainly notify the authors about these errors and enter them into this database . This base can serve as a source of inspiration for many articles ( example ). So, we recommend using this resource as a source of error examples for preparing presentations, writing articles, books, or when developing coding standards.

We wish you a hopeless code. And to be aware of new checks, follow us on Twitter: @Code_Analysis .