Ownership types for safe programming: preventing data races and deadlocks

By Chandrasekhar Boyapati, Robert Lee, Martin C. Rinard. Conference on Object-Oriented Programming Systems, Languages, and Applications, 2002

626 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Hardware and Architecture

View Paper: https://www.semanticscholar.org/paper/53d40f31d0234ef4740a9ece337974fdce722ca2

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 Hardware and Architecture

Citations in the corpus

Verification of Object-Oriented Programs with Invariants (2003, methodology): “It would be interesting to investigate the adaptation of our methodology to concurrent programming, since, for example, our methodology provides support for reasoning about object references and reentrancy (see, e.g., [ 5 ] for another methodology for concurrent programming based on ownership).”
Resources, Concurrency and Local Reasoning (2004, methodology): “The typing schemes were originally developed to account for encapsulation, but were then adapted as well to the problem of ruling out race conditions [ 6 ].”
RacerX: effective, static detection of race conditions and deadlocks (2003, background): “While recent efforts have made progress in addressing some of these limitations [1, 19], in the end a language approach to protection is rather drastic: all code must be written in the language to get any benefits from it, which prevents system builders from choosing any other language that may bett”
The Spec# Programming System: An Overview (2004, background): “Similar effects have been achieved by ownership types and other alias-confinement strategies (e.g., [16, 11 ]).”
Checking Interference with Fractional Permissions (2003, background): “(For example, consider the lock checking of Flanagan and Abadi [6], or Boyapati et al [7] [8].)”
KISS: keep it simple and sequential (2004, background): “This approach has been extended [6, 5] and adapted to other languages [22].”
A type and effect system for atomicity (2003, background): “This approach has been extended [7, 5] and adapted to other languages [24].”
A type and effect system for deterministic parallel Java (2009, background): “Several researchers [11, 3, 28] have described effect systems for enforcing a locking discipline in nondeterministic programs, to prevent data races and deadlocks.”
AVIO: detecting atomicity violations via access interleaving invariants (2006, methodology): “Static data race detection techniques include race type-safe systems [3, 10], static-versions of the lockset algorithm [8] and model checking techniques [17].”
Effective static race detection for Java (2006, background): “…and Subject Descriptors D.2.4 [Software Engineering]: Software/Program Veri.cation Reliability; D.2.5 [Software Engineering]: Testing and Debugging Debugging aids General Terms Experimentation, Reliability Keywords static race detection, Java, synchronization, concurrency, multi-threading 1.”
Learning from mistakes: a comprehensive study on real world concurrency bug characteristics (2008, neutral): “(1) Concurrency bug detection Most previous concurrency bug detection research has focused on detecting data race bugs [7, 10, 31,33,37,42] and deadlock bugs [3,10,37].”