Ok, I will try it out. Those concurrency checks sound especially interesting. One thing however, I just did a quick look at the site and counted 339 different problems that FindBugs can detect. Doing a similar count for IntelliJ IDEA is a little more difficult because it has inspections for a whole bunch of languages, but it has at least 650 Java inspections. At first glance it seems IDEA can find more bugs, that is why I asked this question. Is this a case where I should judge by the quality not the quantity?
Thanks, Bas On Sep 4, 5:03 pm, Dick Wall <[EMAIL PROTECTED]> wrote: > The answer is that findbugs finds more bugs. You can see this for > yourself if you want to try it out. You can either use this link: > > http://findbugs.cs.umd.edu/demo/jnlp/findbugs.jnlp > > to start a webstartable findbugs for yourself, or head on over to > > http://findbugs.sourceforge.net/ > > for more information and to download a non-webstart version. > > It's really easy to use, just point it at the class files for your > code, and to the source files (so that it can show you the bad code). > Findbugs works on the bytecode, not the source, and this seems to make > it a little more complete for a lot of bug detection. > > The bugs it found in particular were related to concurrency errors > (findbugs has been doing a lot of work in this area recently) so it > was able to turn up inconsistent synchronization for example, or other > dodgy code related to that. It also turned up several cases of other > concurrency issues which turned out to be genuine. Other things it > found were potentially dangerous incorrect use of read() operations > (ignoring the return parameter), and lots more - just try it on your > own code. One thing in particular that the IDEA analysis has a habit > of doing is giving up on complex algorithms, findbugs tries harder and > digs deeper. > > Anyway, if you have a bit of non-trivial code, and you have got it to > 0 warnings in IDEA, run findbugs on it. I would bet it will find more > problems and some of the findings will almost certainly be valuable. > > Cheers > > Dick > > On Sep 4, 5:14 am, Bas Leijdekkers <[EMAIL PROTECTED]> wrote: > > > In Java Posse #201 Dick Wall mentions that he finds IntelliJ IDEAs > > "static analysis is nowhere near as good as FindBugs". As a daily user > > of IntelliJ IDEA and implementor of a few of its inspections, but not > > having much familiarity with FindBugs, I wonder what he is missing. > > What features are in FindBugs that are missing from IntelliJ IDEAs > > static analysis? What features are much better in Findbugs? Maybe some > > bug reports and/or feature requests need to be filed with Jetbrains? > > Are there any FindBugs users here who can educate me? Dick, would you > > explain? > > > Bas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
