Finding Bugs Is Easy 66
daveho writes "My advisor and I are working on a tool to automatically find bugs in Java programs. One of the interesting results of our work is that we've found hundreds of real bugs in production code using extremely simple techniques. We believe that automated tools, if used more widely, could prevent a lot of bugs from making it in to production systems."
Bugs in Java code? Inconceivable! (Score:3, Funny)
I thought it was impossible to write bugs in Java - nature's most perfect language! After all, all the Java bigo^H^H^H^Hzealot^H^H^H^H^H^Hexperts have always said that all software problems would vanish if we would just use their perfect language.
(/me removes tongue from cheek)
I just hope that the myriad and varied Java bigots out there will take this to heed: No language can prevent you from making mistakes.
(NOTE: I most emphatically do NOT assert that a language cannot make certain classes of errors more difficult to make!)
(NOTE 2: I also do not assert that all people who use Java, or promote the use of Java are bigots.)
There is no substitute for experience, careful design, and methodical testing.
The obvious solution... (Score:4, Funny)
FindBugs? (Score:4, Funny)
They need to pick a name like "||gazm", "JizMop", or "Mozilla" like all the other cool OS projects. I'm sure they'll learn their lesson soon.
Re:FindBugs? (Score:3, Funny)
What a perfect name for a logic-based language or boolean calculator!
Re:FindBugs? (Score:3, Funny)
Suggestions to daveho (Score:2, Funny)
I got a few hints from the screenshots and changelist... but I need more!
* infrastructure for doing dataflow analysis
* tracking of locks for inconsistent synchronization detector
* a few general cleanup fixes in the screenshot
The first 2 especially sound interesting... but not quite enough for me to download a 0.5 version release and slog through the source code.