|
I see there are many proprietary lint lookalikes with typical "enterprise" price ranges. But is there any point in paying the money they ask for a static C source analyzer instead of using an open source tool? Or rewording it, what tool do you recommend for that task? PS: This is embedded development so we won't use any dynamic features, and pure C89. |
|||
|
|
|
LLVM + Clang. It has fantastic support for static analysis and has a very liberal license. http://clang-analyzer.llvm.org/ Instructions for building from source on platforms other than Mac OS X: |
|||
|
|
|
Unless you set it up very carefully and at the start of development I have generally found that Lint swamps you in false positives. However it does have some useful features, such as MISRA compliance checking. At work we have standardised on Coverity. It's not cheap, but it has good coverage and a very low false positive once configured for your compiler, which is vital if you are applying it to large code bases. |
|||
|
|
|
A decent list of open-source or non-commercial products is over at Wikipedia. |
|||
|
