On Fri, Mar 5, 2010 at 12:50 PM, Mark Bucciarelli <mkb...@gmail.com> wrote: > On Fri, Mar 5, 2010 at 12:45 PM, Ted Unangst <ted.unan...@gmail.com> wrote: >> >> http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis > > So which would you use to find all fopen() > calls where the return value was ignored?
>From the free list, clang and splint could find that bug. It's probably not hard to make sparse find it either. You could write a gcc4 plugin to do it. For money, Klocwork and Coverity can definitely find it, probably/possibly Ounce, Grammatech, and Fortify too.
