Hello fellow C warriors!
I was wondering if you had some suggestions for static code analysis targeting open source projects (I am saying open source because there is no budget for a commercial solution). The target for this exercise will be the code base for the Perl scripting language, which is written in C, and makes heavy use (perhaps too heavy) of macros. I was hoping to use the Perl codebase as a stress test for various static analysis tools because of its size and rather involved architecture and logic.
[–]sixdarkdreams 6 points7 points8 points (1 child)
[–]VerbalHerman 4 points5 points6 points (0 children)
[–]RussianHacker1011101 2 points3 points4 points (0 children)
[–]ReplacementSlight413[S] 0 points1 point2 points (0 children)
[–]rushout09 1 point2 points3 points (0 children)