| 
|
QuoteRef: hoveD12_2004
topics >
all references >
Topic:
debugging by usage rules
Topic:
programming style
Topic:
automated tests of specifications and designs
Topic:
consistency testing
Group:
security
Topic:
preventing accidental errors
Topic:
safety, liveness, and system properties
Topic:
bugs
Topic:
race conditions
Group:
parallel processing
Reference
Hovemeyer, D., Pugh, W., "Finding bugs is easy", ACM SIGPLAN Notices, 39, 12, pp. 92-106, RL http://findbugs.sourceforge.net. Google
abstract ;;Quote: find serious mistakes and usage errors by detecting bug patterns, i.e., code idioms that often error; easily implemented
93 ;;Quote: a bug checker uses static analysis to find correctness violations; while a style checker identifies code style violations
93 ;;Quote: FindBugs identifies 50 bug patterns using the inheritance hierarchy, linear code scan, control flow graph, and dataflow analysis; implemented with BCEL; most tests are short
94 ;;Quote: bug detectors for thread correctness, performance issue, security violation, usage bug, dropped exception, null pointer, open stream, unchecked return, unconditional wait
102 ;;Quote: everyone makes dumb mistakes; a huge number of bugs are just one step away from a syntax error; e.g., typing || instead of &&
102 ;;Quote: use bug checkers for latent bugs; e.g., a covariant equals method works until someone adds the class to a map or set; another latent bug is hashcode/equals
102 ;;Quote: programming with threads is difficult; misuse of concurrency is widespread; use a bug checker to catch concurrency problems
Topic: debugging by usage rules (41 items)
Topic: programming style (47 items)
Topic: automated tests of specifications and designs (12 items)
Topic: consistency testing (60 items)
Group: security (23 topics, 874 quotes)
Topic: preventing accidental errors (37 items)
Topic: safety, liveness, and system properties (22 items)
Topic: bugs (66 items)
Topic: race conditions (33 items)
Group: parallel processing (41 topics, 1125 quotes)