C and C++ programmers tend to make mistakes when writing code.
Many of these mistakes can be found using -Wall, asserts, tests, meticulous code review, IDE warnings, building with different compilers for different operating systems running on different hardware configurations, and the like. But even all these means combined often fail to reveal all the bugs. Static code analysis helps improve the situation a little. In this post, we will take a look at some static analysis tools.
Below is a list of the common static code analyzers:
- CppCheck
- Clang Static Analyzer
- PVS-Studio
- Coverity Scan
- Splint
- Oclint
Description and principle of operation of each analyzer, read the article: An Overview of Static Analyzers for C/C++ Code | How Not To Code
