Why Don't Software Developers Use Static Analysis Tools to Find Bugs?

Re:Why Don't Software Developers Use Static Analysis Tools t... by 72deluxe on Friday June 26, 2015 @04:35AM (#9783016)

I do! For cheapness, Flawfinder, CPPCheck, and Product > Analyze in xcode (thanks clang) (the walkthroughs in xcode of how they deduced the problem are really great, blue arrows everywhere, very neat).

EDIT: Additionally, given the changes in C++11 we should be able to push all the work onto the compiler for checking type problems, remove dangerous operations, dangling pointers, naked new/delete and avoid casting where possible. It would make for bug-free software. I know someone who writes their C++ like it is late 80s C and firstly, it's horrible to read. And secondly, it does really dangerous things.

[ Parent | on HN ]

Re:Why Don't Software Developers Use Static Analysis Tools t... by roel_v on Friday June 26, 2015 @05:02AM (#9783087)

I refactored some code this week that used realloc to allocate memory for a 'vector' (which was a typedef for float*), and then a loop with additional realloc's to allocate memory for each element in that vector, to end up with a matrix 8| This is code that was written in the last few years, too. Welcome to academia :(

[ Parent | on HN ]