Bugs. Bugs never change

You have opened an article that you must link to on Twitter. Or place in your favorite programmer group. This will benefit both us and open source projects. For programmers around the world to learn about PVS-Studio, we check open source projects and do them better. And at the same time we are writing interesting and useful articles. The more people learn about our articles, the more pleasant it will be for us to do this and the more projects we will check. Joint profit.

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

Often you can see notes about checking the project using the static analyzer X. However, these are either general words, or a mixture of analyzer messages and diff results. It’s not interesting to read empty ads. And from the report on 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 fix it and how to avoid such errors if possible. Here are the results of our many years of work: An

updated list of articles in which we talk about errors found using 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 about the dark corners of the C ++ language.

To be interesting, we prefer well-known programs. For example, you may encounter errors in the code for 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 are sure to notify the authors of these errors and enter them here in 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 examples of errors for preparing presentations, writing articles, books, or developing coding standards.

We wish you a codeless code. And to keep abreast of new checks, follow us on Twitter: @Code_Analysis .