Group items tagged

We regularly check various open-source projects with PVS-Studio and send analysis results to developers and usually describe them in our posts as well. Besides, we add them into our bug database. This database is posted below on this page. The bugs are grouped according to the number of the diagnostic rule that is used to detect them. This number is given in the left column. Click on it to see the diagnostic rule description in the documentation. The right column contains a link to the corresponding error samples. Some diagnostics haven't detected any bugs in open-source projects yet. The lower you are in the list, the more diagnostics with no error samples there will be. The reason is simple: the later a certain rule had been added, the fewer projects were analyzed with this rule included into the rule set and therefore the fewer chances for it to demonstrate its capabilities.

The PVS-Studio team has analyzed over 200 open-source projects with their static code analyzer. Among them are such titles as Unreal Engine, Php, Haiku, Qt, and even Linux. In each of these projects, bugs of varying severity were detected. The team regularly reports the analysis results in their blog. Each post is a separate article of several pages, describing in detail each of the bugs found and giving recommendations on how to fix them. The PVS-Studio team decided to go further to create a service of tips and recommendations on C/C++ usage, CppHints.com, in addition to the practice of writing articles. Within the scope of this service, the team publishes 1 recommendation/tip per day. Each publication delivers concentrated information on C/C++ programming approaches and techniques used in various situations and includes examples of correct and incorrect language use from over 200 open-source projects.

We have checked the Windows 8 Driver Samples pack with our analyzer PVS-Studio and found various bugs in its samples. There is nothing horrible about it - bugs can be found everywhere, so the title of this article may sound a bit high-flown. But these particular errors may be really dangerous, as it is a usual practice for developers to use demo samples as a basis for their own projects or borrow code fragments from them.

Welcome About Lazarus Status Screenshots Updated Feb 20, 2001 How to participate How to code Bug Tracking FAQ Documentation Mailing list Download

Welcome About Lazarus Status Screenshots Updated Feb 20, 2001 How to participate How to code Bug Tracking FAQ Documentation Mailing list Download

The Clang Static Analyzer is source code analysis tool that find bugs in C and Objective-C programs.

For the purpose of testing our C/C++ analyzer PVS-Studio, we often check various open-source projects and publish reports about bugs we have found. It is obvious that we seek projects of large sizes (hundreds of thousands of code lines), as there is little to be tested and caught in just a few dozens of files. We already had opportunities to test large collections consisting of hundreds of small open-source projects, for example sets of test samples for various SDKs and Frameworks. We are especially interested in checking such collections to see how the analyzer supports various specific code constructs, Visual C++ project subtypes, and so on.

PVS-Studio is a static analyzer that detects errors in source code of C/C++/C++11 applications. There are sets of rules included into PVS-Studio: General-purpose diagnosis Detection of possible optimizations Diagnosis of 64-bit errors (Viva64) Diagnosis of parallel errors (VivaMP)

The best way to advertise a static code analyzer is to find errors in open source projects and share them with the world. We have been using this method for a long time while promoting our tool PVS-Studio. If you have ever heard of PVS-Studio, it was most likely from our articles reporting on the checks of such projects as Chromium, WinMerge, TortoiseSVN, Apache HTTP Server, Qt, Clang and many others.