Coverity Scan VS Clang Static Analyzer

Coverity Scan Reviews

Clang Static Analyzer Reviews

Coverity Scan mentions (4)

• I created this point of sale system for restaurants and hospitality. The All-In-One has a 15.6" touchscreen running a Raspberry Pi Compute Module 4L and is made by Chipsee in Bejing, China. I'm helping a friend install it in a restaurant on the St. Lawrence River where he is the Executive Chef.

  You can use Coverity for free on open source code. I use it on an app I open sourced for packet processing. https://scan.coverity.com/. Source: over 2 years ago

• Free for dev - list of software (SaaS, PaaS, IaaS, etc.)

  Scan.coverity.com — Static code analysis for Java, C/C++, C# and JavaScript, free for Open Source. - Source: dev.to / over 2 years ago

• CDN dollar just hit 6 year high.

  I personally remember Coverity Scan being completely offline for like 6 months while they tried to deal with infrastructure abuse from people mining bitcoin on their computing clusters. Source: almost 3 years ago

• GCC 10.3 has been released

  > Does anyone know any good static analysers other than gcc's or clang's? Visual C++ as well, because since the XP SP2 issues, Microsoft has come up with SAL, which you can also use on your own code, https://docs.microsoft.com/en-us/cpp/code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects?view=msvc-160 Then specialized tooling just for this purpose, just two examples, https://scan.coverity.com/... - Source: Hacker News / about 3 years ago

Clang Static Analyzer mentions (7)

• Improvements to static analysis in GCC 14

  Clang has a similar tool, the Clang Static Analyzer: https://clang-analyzer.llvm.org/. - Source: Hacker News / 16 days ago

• Memory Safe or Bust?

  Continuous Integration and Continuous Deployment [CI/CD] pipelines play a crucial role in enforcing code quality, especially when working with memory-unsafe languages. By integrating automated dynamic analysis tools like Valgrind or AddressSanitizer, static analysis tools like Clang Static Analyzer or cppcheck, and manual code review processes, developers can identify and mitigate many memory-related... - Source: dev.to / 23 days ago

• Static Code analysis

  No one static analyzer catches everything. It's best to run multiple. Popular ones are cppcheck, clang-analyzer, GCC static analyzer in GCC 10+, flawfinder, lizard. Source: about 1 year ago

• Checked C

  With "cross translation units" (CTU) analysis a static analyzer could derive a constraint on `some_function` return value and check this against the array size to detect a possible bug. The Clang static analyzer [1], used through CodeChecker (CC) [2], do support CTU (enabled with `--ctu`). I'm very happy with the result on the code I'm working on. Of course this is not magic, and it's important to understand the... - Source: Hacker News / over 1 year ago

• What's in your tool belt?

  Cppcheck and Clang Analyzer: statically analyze your code to find bad style and bugs (undefined behavior) respectively. Clang Analyzer can actually be frighteningly clever and has a low false positive rate (unlike most other non-commercial static checkers). Source: almost 2 years ago