Opened 17 years ago
Last modified 11 years ago
#65 new task
Use FindBugs to detect possible bugs
Reported by: | Owned by: | David Aspinall | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | 1:pg-eclipse | Keywords: | |
Cc: |
Description
All developers are recommended to use FindBugs to help detect possible bugs statically:
http://findbugs.sourceforge.net/ http://findbugs.cs.umd.edu/eclipse (update site)
Lines which FindBugs flags as being possible bugs which are not corrected should be tagged with the FindBug abbreviation, and either a FIXME or an OK assertion, e.g.:
if (foo!=null) { // DC: OK
is an assertion by the developer that the FindBug warning should be ignorable. This helps in reviewing the complete set of warnings later.
Particularly useful checks where many bugs have been found are:
- NP possible null pointer problems (esp dereferencing pointers that are known to be null)
- ES string equality using == instead of .equals
- RCN redundant null check
- DC possible use of double-checked locking
Change History (5)
comment:1 Changed 17 years ago by
Priority: | major → critical |
---|---|
Summary: | Use !FindBugs to detect possible bugs → Use FindBugs to detect possible bugs |
comment:2 Changed 17 years ago by
Priority: | critical → minor |
---|
comment:3 Changed 17 years ago by
Milestone: | → Future |
---|---|
Priority: | minor → major |
comment:4 Changed 17 years ago by
Milestone: | Future → Every |
---|
comment:5 Changed 11 years ago by
Milestone: | Every |
---|
Note: See
TracTickets for help on using
tickets.
Milestone Every deleted