Atomizer: a dynamic atomicity checker for multithreaded programs

By Cormac Flanagan, Stephen N. Freund. 18th International Parallel and Distributed Processing Symposium, 2004. Proceedings., 2004

497 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Computer Networks and Communications, Hardware and Architecture

View Paper: https://www.semanticscholar.org/paper/212b23c3c50c398213503509155b0e347648cc0f

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Computer Networks and Communications

In Hardware and Architecture

Citations in the corpus

Effective static race detection for Java (2006, background): “Recent work on verification of concurrent programs has focused on checking atomicity [2, 18, 22, 24–26, 44, 51, 52].”
AsyncShock: Exploiting Synchronisation Bugs in Intel SGX Enclaves (2016, background): “A large number of tools were proposed to help developers find different kinds of synchronisation bugs, such as atomicity violations [6, 8, 16], order violations [9, 17, 32] and data races [20, 31].”
FastTrack: efficient and precise dynamic race detection (2009, background): “For example, atomicity checkers, such as ATOMIZER [16] and VELODROME [17], and determinism checkers, such as SINGLETRACK [32], can ignore race-free memory accesses.”
Search Based Software Engineering (2013, unknown): “Descriptions of some of these studies can be found in books [20,16,13,84], dedicated conference proceedings [101,49,12,83,43,95], and domain-specific books, journals and proceedings.”
Learning from mistakes: a comprehensive study on real world concurrency bug characteristics (2008, unknown): “Furthermore, data-race free does not mean concurrency bug free [12, 23].”
Iterative context bounding for systematic testing of multithreaded programs (2007, methodology): “Analysis tools: Researchers have developed many dynamic analyses, such as data-race detection [24] and atomicity-v iolation detection [6], for finding errors in multithreaded software .”
CTrigger: exposing atomicity violation bugs from their hiding places (2009, methodology): “CTrigger then uses minimum execution perturbation to exercise low-probability interleavings and expose dif.cult-to-catch atomicity violation.”
Race directed random testing of concurrent programs (2008, background): “Such sets of problematic statements could be provided by a static or dynamic analysis technique [23, 22, 2].”
A Survey on Software Fault Localization (2016, background): “Concurrent programs suffer most from three kinds of access anomalies: data race [32], [321], atomicity violation [110], [113], [115], and atomic-set serializability violations [24], [44].”
RELAY: static race detection on millions of lines of code (2007, methodology): “atomicity[11] violations in Java code [29, 12], and the use of automated replay to determine whether a given dynamically det ect d race is benign or harmful [21].”
AVIO: detecting atomicity violations via access interleaving invariants (2006, unknown): “Most state-of-the-art techniques [11, 12] for detecting these bugs require programmers’ annotations on atomic regions, which is too time-consuming for programmers.”