PVS-Studio might be a bit more popular than Cppcheck. We know about 10 links to it since March 2021 and only 10 links to Cppcheck. 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 / 2 months 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: 11 months 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 1 year 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 1 year 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 1 year ago
The analyzer has found various types of errors in the project. So, we'd like to look at them from different angles. That's why I'll publish several articles on different topics. The first one is dedicated to the Best button in the PVS-Studio plugins. - Source: dev.to / 16 days ago
One of the ways to create better and more secure code is to use static analyzers such as PVS-Studio. The tool provides code analysis for the C, C++, C#, and Java programming languages. - Source: dev.to / about 1 month ago
I checked the code with the PVS-Studio analyzer using the plugin for Visual Studio. - Source: dev.to / 10 months ago
I'm working on PVS-Studio. It's a code analysis tool detects both coding errors and security flaws (SAST). So, I'd like to know more about what teams expect from SAST solutions. Source: about 1 year ago
And yet SAST is another essential step-up that can help reduce reputational and financial risks. If you are building SSDLC, SAST tools should be a mandatory part of the DevSecOps pipeline. - Source: dev.to / about 2 years 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...
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free
Parasoft C/C++test - Ensure compliance with a variety of functional safety, security, and coding standards in embedded C/C++ software.
lgtm.com - lgtm.com is a platform for code analytics.
Flawfinder - David A. Wheeler's Page for Flawfinder