| 
|
QuoteRef: hoveD7_2004
Topic:
race conditions
Group:
parallel processing
Topic:
managing shared memory
Topic:
debugging by usage rules
Topic:
concurrency
Topic:
deadlocks
Topic:
waitfor condition in parallel processing
Reference
Hovemeyer, D., Pugh, W., "Finding concurrency bugs in Java", PODC Workshop on Concurrency and Synchronization in Java Programs, July 2004. Google
Notes
preprint, pp 10.
2 ;;Quote: simple analysis find obvious synchronization errors; programmers do not understand synchronization and they avoid using synchronization
2 ;;Quote: the Java memory model is not sequentially consistent; optimization and inlining can have non-local effects, making eyeballing race conditions very difficult
3 ;;Quote: the most common synchronization error was ignoring read synchronization; data may be out-of-date or uninitialized
3 ;;Quote: binary operations on shared objects must synchronize both objects; all threads must use the same lock acquisition order
5 ;;Quote: a wait on multiple conditions should be in a loop that tests the conditions; otherwise no guarantee that the conditions hold after the wait
6 ;;Quote: concurrency bug patterns: mismatched wait, double locking, notify vs. notifyAll, run vs. start, mutable lock, naked notify, spin wait
Topic: race conditions (33 items)
Group: parallel processing (41 topics, 1125 quotes)
Topic: managing shared memory (74 items)
Topic: debugging by usage rules (41 items)
Topic: concurrency (33 items)
Topic: deadlocks (21 items)
Topic: waitfor condition in parallel processing (20 items)