Based on our record, PVS-Studio should be more popular than Cppcheck. It has been mentiond 17 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / about 1 year ago
Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: almost 2 years ago
For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: about 2 years ago
Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: about 2 years ago
Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 2 years ago
The court is silent. Even the judge is speechless. The most dangerous criminals of the year have been apprehended. The only thing left is to destroy them, but that's another story... However, we wouldn't have been able to find these errors without the help of our trusty detective—the PVS-Studio analyzer. - Source: dev.to / 4 months ago
As mentioned above, I analyzed the project using the PVS-Studio static analyzer. The checked code matches the 3d30b2e commit. - Source: dev.to / 5 months ago
If I understand correctly, LLVM is already regularly checked with Coverity Scan Static Analysis and Clang Static Analyzer. PVS-Studio would look great next to the above tools :) That would be a horse of a different colour! - Source: dev.to / 5 months ago
The above scope characteristic can be an unexpected problem for a developer. For example, legacy code with irrelevant logic may cause issues when executed (especially in a running application). Certain tools that detect such non-obvious errors can help you prevent this. Those are static code analyzers. This update inspired us to add a new diagnostic rule for our C# PVS-Studio analyzer, in addition to hundreds of... - Source: dev.to / 6 months ago
So, PPSSPP is a powerful tool that enables fans of classic PSP games to enjoy them with improved graphics and the convenience of modern devices. Since PPSSPP is an open-source project, we were eager to check it using our tool. - Source: dev.to / 7 months ago
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
Clang Static Analyzer - The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C++, and Objective-C...
Parasoft C/C++test - Ensure compliance with a variety of functional safety, security, and coding standards in embedded C/C++ software.
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
lgtm.com - lgtm.com is a platform for code analytics.
Polyspace - Polyspace is a suite of static code analysis products developed by Matlab to help software developers, QA Testers, and engineers find critical problems in their code and fix them before they become a serious threat.