[cfe-dev] Coverity vs Clang Static analyzer

[Jean-Daniel Dupas]

Actually, one of the main feature I like in Coverity is cross module analysis. 

Getting a warning when you pass a potentially null parameter to a method that try to dereference it unconditionally help me to catch a lot of issues.

When using clang, I also miss some simple warnings like uninitialized C++ members in constructor.


Le 20 févr. 2014 à 07:42, G Raghuram <contactraghu at gmail.com> a écrit :

> Hello,
> 
> Synopsys has decided to acquire. We are a direct competitor of Synopsys and have been using coverity. As I work for a direct competitor, I believe from now on, we will have to decrease our dependence on Coverity.
> 
> Can someone please comment on features of Clang static analyzer vs Coverity? Does coverity catch any extra errors or can we just do a drop-in replacement.?
> 
> Thanks
> GRR
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-- Jean-Daniel