An always up-to-date list of articles describing errors that we find in open source projects with PVS-Studio analyzer
Rus
  1. HOME

An always up-to-date list of articles describing errors that we find in open source projects with PVS-Studio analyzer


It contains articles describing the errors that were discovered by analyzing different open-source projects.

We are friendly to open-source projects. We do our best to let their authors know about defects we find and grant them temporary free licenses for our tool if necessary.

Picture 1

Below is a list of open-source C, C++ and C# projects for Windows and Linux we have analyzed by now with PVS-Studio:

Operating systems

Microsoft projects

Web Browsers

GameDev

Compilers

Programming languages

Development

Libraries

Graphics

Music Software

Messengers

Other projects

It's not entirely without any reward that we analysis all these projects. The reports we publish serve as an advertisement for our tools and our company. We make no secret of it. But I believe it's the best advertisement you've ever seen! PVS-Studio does help the open-source community.

You may notice that the above mentioned articles are very different in size. Well, there is an explanation to that. For example, when writing the first article about ReactOS, our analyzer had much fewer diagnostic rules than at the time of the second analysis. Within the time period between the two analysiss, the tool has learned to find several times more bugs. Because of that, our articles reporting analysis results will only grow larger in time. Now we have to skip numerous bugs that don't look too impressive and convincing in order not to turn an article into a reference book.

We also keep a bug database at our website. I think many of you will find it interesting wandering about it. But what's most interesting, you can use it as a resource to work out coding standards and new recommendations for textbooks and articles on programming. It is now waiting for its McConnell to come and use it as soil to raise a book of the "50 Tips on How Not to Drop a Clanger" style.


Do you make errors in the code?

Check your code
with PVS-Studio

Static code analysis
for C, C++, and C#

goto PVS-Studio;

Bugs Found

Checked Projects
321
Collected Errors
12 244

Qt

C++ 
int gx = gm.x.toInt();
int gy = gm.y.toInt();
int iw = gm.width.toInt();
int ih = gm.height.toInt();
if (iw <= 0 || iw <= 0)
  return 0;

UnrealEngine

C++ 
switch ( BlendMode )
{
case Opaque:
  BackgroundColor.A = 1.0f;
case Masked:
  BackgroundColor.A = 0.0f;
}

Xamarin

C# 
get {
  return Left == 0 &&
         Top == 0 &&
         Right == 0 &&
         Left == 0;
}

Chromium

C++ 
void Explode(bool is_local,
  Exploded* exploded) const
{
  ....
  ZeroMemory(
    exploded,
    sizeof(exploded));
  ....
}

Qt

C++ 
int gx = gm.x.toInt();
int gy = gm.y.toInt();
int iw = gm.width.toInt();
int ih = gm.height.toInt();
if (iw <= 0 || iw <= 0)
  return 0;

UnrealEngine

C++ 
switch ( BlendMode )
{
case Opaque:
  BackgroundColor.A = 1.0f;
case Masked:
  BackgroundColor.A = 0.0f;
}

Xamarin

C# 
get {
  return Left == 0 &&
         Top == 0 &&
         Right == 0 &&
         Left == 0;
}

Chromium

C++ 
void Explode(bool is_local,
  Exploded* exploded) const
{
  ....
  ZeroMemory(
    exploded,
    sizeof(exploded));
  ....
}
All projects →

Recent Posts

All articles →

It's interesting!