Findbugs is a quite interesting gadget that can analyze the common "bad code" in the Java program - these code may be efficient (for example, unnecessary objects), may also have hidden dangers in security or stability ( For example, inappropriate synchronization, unstoped file handle). I checked JUnit with Findbugs and found several small problems; and checking the J2SE 1.4.2 Runtime was a lot of findings. Your own procedure, is it to do it?
At present, this little thing can only check .class files in .lar files, can't say a little shortcomings, and how much trouble is used. Are you interested in doing it to do it?
----------------
FindBugs is a program which looks for bugs in Java code. It can detect various coding "mistakes" including thread synchronization problems and misuse of API methods. It includes both Swing and command line interfaces.
The New Version Adds New Bug Detectors:
- Places Where a null Pointer Might Be dereferenced
- I / O streams That Are Opened, Do Not Escape The Method, And Are Not Closed on All Paths Out of the Method
- Methods That Can Return Null INSTEAD OF A Zero-Length ARRAY
- use the == or! = Operators to Compare String Objects
Other Changes in this Version:
- Command Line Interface Can Save Bugs As XML
- GUI CAN SAVE BUGS TO AND Load Bugs from XML
- AN "Annotations" Window in The Gui Allows The User To Add Textual Annotation to bug Reports; these Annotations Are Preserved When Bugs Are Saved As XML
- in this Release
- Completely Rewrote The Control Flow Graph Builder, Hopefully for The Last Time
- Simplified Implementation of Control Flow Graphs, Which SHOULD Reduce Memory Use and Possibly Improve Performance
- Improvements to Command Line Interface (List bug priority, specify aux classpath, specify project to analyze)
- Various bug fixes and enhancements
Check Out the open sourcefindbugs
