static code analysis tool

[ETRO_SSN583]

Anyone experimented with a static code analysis tool to detect simple faults,

   

typing, pointer, array bounds, memory issues ? Call graphs, etc..

       

I see on web a Stanford and some other study of tools, free and commercial, and

   

looks like only commercial produces worthwhile analysis. But big $$$$.

       

Regards, Dana.

[HeLi_263931]

There is always lint, should be available with cygwin or any linux distribution 🙂 (Or you pay $389 here: http://www.gimpel.com/html/pcl.htm ) Wikipedia is helpful as usual: http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C.2FC.2B.2B

   

I remember an interesting write-up by John Carmack about using static code analysis within id software: http://www.altdevblogaday.com/2011/12/24/static-code-analysis/ . it reflects my experiences when using such tools on large code bases - one needs to be careful not to overwhelm the developers.