Splint VS Clang Static Analyzer

Whenever I see people talk about the portability or compatibility advantages of C, I'm reminded of how "even C isn't compatible with C", because you typically aren't talking about up-to-date GCC or LLVM on these niche platforms... you're talking about some weird or archaic vendor-provided compiler... Possibly with syntax extensions that static analyzers like splint will choke on. (Splint can't even understand near... Source: about 1 year ago

Huh. I think I actually needed to use the equivalent position for certain splint annotations in my C retro-hobby project. Source: about 1 year ago

I often like to say that Rust's bindings are a way to trick people into writing the compile-time safety annotations that they didn't want to write for things like splint. (Seriously. Look into how much splint is capable of checking with the correct annotations.). Source: about 1 year ago

Linters like Splint [0] can do that for C. I’m not saying that Rust’s built-in approach isn’t better, but please be careful about what exactly you claim. [0] http://splint.org/. - Source: Hacker News / over 1 year ago

(Sort of like how, for my DOS hobby project, I use splint to require explicit casts between typedefs so I can use the newtype pattern without having to manually reach into wrapper struct fields in places that don't do conversions.). Source: over 1 year ago

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

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 / 28 days ago

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

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

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