2010
DOI: 10.1007/978-3-642-16901-4_39
|View full text |Cite
|
Sign up to set email alerts
|

A Modular Scheme for Deadlock Prevention in an Object-Oriented Programming Model

Abstract: Abstract. Despite the advancements of concurrency theory in the past decades, practical concurrent programming has remained a challenging activity. Fundamental problems such as data races and deadlocks still persist for programmers since available detection and prevention tools are unsound or have otherwise not been well adopted. In an alternative approach, programming models that exclude certain classes of errors by design can address concurrency problems at a language level. In this paper we review SCOOP, an… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
11
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 13 publications
(11 citation statements)
references
References 10 publications
0
11
0
Order By: Relevance
“…Scoop Analysis/Verification. Various analyses for Scoop programs have been proposed, including: using a Scoop virtual machine for checking temporal properties [29]; checking Coffman's deadlock conditions using an abstract semantics [7]; and statically checking code annotated with locking orders for the absence of deadlock [39]. In contrast to our work, these approaches are tied to particular (and now obsolete) execution models, and do not operate on (unannotated) source code.…”
Section: Related Workmentioning
confidence: 99%
“…Scoop Analysis/Verification. Various analyses for Scoop programs have been proposed, including: using a Scoop virtual machine for checking temporal properties [29]; checking Coffman's deadlock conditions using an abstract semantics [7]; and statically checking code annotated with locking orders for the absence of deadlock [39]. In contrast to our work, these approaches are tied to particular (and now obsolete) execution models, and do not operate on (unannotated) source code.…”
Section: Related Workmentioning
confidence: 99%
“…Scoop Analysis / Verification. Various analyses for Scoop programs have been proposed, including: using a Scoop virtual machine for checking temporal properties [OTHS09]; checking Coffman's deadlock conditions using an abstract semantics [CM17]; and statically checking code annotated with locking orders for the absence of deadlock [WNM10]. In contrast to our work, these approaches are tied to particular (and now obsolete) execution models, and do not operate on (unannotated) source code.…”
Section: Related Workmentioning
confidence: 99%
“…A client object must acquire an exclusive lock on a separate object before invoking it through a routine. SCOOP was ported to Java [44] but is not inherently deadlock-free [45]. Some recent lock-inference techniques are deadlock-free, yet they require the programmer to provide a semantic description of methods [46].…”
Section: Related Workmentioning
confidence: 99%