When Daniel Hax ran Coverity and Clang against the curl source code, he found that the each "tool detected several issues the other didn’t spot."
Coverity – very accurate reports and few false positives
clang-analyzer – awesome reports, missed slightly too many issues and reported slightly too many false positives [1]
You'll find similar results in PVS Studio vs clang[2] and PVS Studio vs Coverity.[3] If code quality is important to your organization, than one tool is probably not enough. If it's vital, you may want to consider another language such as Haskell or OCaml.
[1] http://daniel.haxx.se/blog/2012/07/12/three-static-code-anal...
Re:Additional C/C++ Tooling
by jschwartzi on Saturday July 25, 2015 @12:54AM
(#9946605)
Just out of curiosity, how big is your org? I've been tempted to suggest Coverity a few times but I always balk at buying tools where the price is listed as $CallSalesAndNegotiate.
I wish we could buy just a couple Coverity licenses, but they want to license the entire organization for something like $200,000.