Sciweavers

KBSE
2005
IEEE

Optimized run-time race detection and atomicity checking using partial discovered types

14 years 5 months ago
Optimized run-time race detection and atomicity checking using partial discovered types
Concurrent programs are notorious for containing errors that are difficult to reproduce and diagnose. Two common kinds of concurrency errors are data races and atomicity violations (informally, atomicity means that executing methods concurrently is equivalent to executing them serially). Several static and dynamic (run-time) analysis techniques exist to detect potential races and atomicity violations. Run-time checking may miss errors in unexecuted code and incurs significant run-time overhead. On the other hand, run-time checking generally produces fewer false alarms than static analysis; this is a significant practical advantage, since diagnosing all of the warnings from static analysis of large codebases may be prohibitively expensive. This paper explores the use of static analysis to significantly decrease the overhead of run-time checking. Our approach is based on a type system for analyzing data races and atomicity. A type discovery algorithm is used to obtain types for as muc...
Rahul Agarwal, Amit Sasturkar, Liqiang Wang, Scott
Added 25 Jun 2010
Updated 25 Jun 2010
Type Conference
Year 2005
Where KBSE
Authors Rahul Agarwal, Amit Sasturkar, Liqiang Wang, Scott D. Stoller
Comments (0)