Healing data races on-the-fly

Křena, Bohuslav; Letko, Zdeněk; Tzoref, Rachel; Ur, Shmuel; Vojnar, Tomáš

doi:10.1145/1273647.1273658

Cited by 50 publications

(38 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some self-healing techniques focus on nonfunctional problems, for instance, Vaidyanathan and Trivedi [2005] propose a technique to address aging problems, Candea et al [2004] address transient problems, Krena et al [2007] focus on concurrency problems. These techniques are complemental to the healing patterns presented in this article that address functional integration faults.…”

Section: Self-healingmentioning

confidence: 99%

Exception handlers for healing component-based systems

Chang

Mariani

Pezzè

2013

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

To design effective exception handlers, developers must predict at design time the exceptional events that may occur at runtime, and must implement the corresponding handlers on the basis of their predictions. Designing exception handlers for component-based software systems is particularly difficult because the information required to build handlers is distributed between component and application developers. Component developers know the internal details of the components but ignore the applications, while application developers own the applications but cannot access the details required to implement handlers in components.This article addresses the problem of automatically healing the infield failures that are caused by faulty integration of OTS components. In the article, we propose a technique and a methodology to decouple the tasks of component and application developers, who will be able to share information asynchronously and independently, and communicate implicitly by developing and deploying what we call healing connectors. Component developers implement healing connectors on the basis of information about the integration problems frequently experienced by application developers. Application developers easily and safely install healing connectors in their applications without knowing the internal details of the connectors. Healing connectors heal failures activated by exceptions raised in the OTS components actually deployed in the system.The article defines healing connectors, introduces a methodology to develop and deploy healing connectors, and presents several case studies that indicate that healing connectors are effective, reusable and efficient.

show abstract

Section: Self-healingmentioning

confidence: 99%

Exception handlers for healing component-based systems

Chang

Mariani

Pezzè

2013

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…This idea is reflected by inserting a new internal state of the shared variables. The modification introduces a small possibility of having false negatives [40,69] but greatly reduces the number of false alarms caused by this object-oriented programming idiom.…”

Section: Detection Of Data Racesmentioning

confidence: 99%

A Uniform Classification of Common Concurrency Errors

Fiedor

Bohuslav

ena

et al. 2012

Computer Aided Systems Theory – EUROCAST 2011

Self Cite

View full text Add to dashboard Cite

Abstract. Nowadays, multi-threaded programs are quite common and so are concurrency errors. Many works devoted to detection of concurrency errors have been published in recent years and many of them presented definitions of concurrency errors that the proposed algorithms are able to handle. These definitions are usually expressed in different terms suitable for a description of the particular considered algorithms and they surprisingly often differ from each other in the meaning they assign to particular errors. To help understanding the errors and developing techniques for detecting them, this report strives to provide a uniform taxonomy of concurrency errors common in current programs, with a stress on those written in Java, together with a brief overview of techniques so far proposed for detecting such errors.

show abstract

“…Krena et al [18] propose two schemes to dynamically heal data races for Java programs. In one scheme, they reduce the probability of races happening by forcing threads that are about to cause racy accesses to yield.…”

Section: Race Tolerationmentioning

confidence: 99%

Hardware support for enforcing isolation in lock-based parallel programs

Ratanaworabhan

Burtscher

Kirovski

et al. 2012

Proceedings of the 26th ACM International Conference on Supercomputing

View full text Add to dashboard Cite

When lock-based parallel programs execute on conventional multicore hardware, faulty software can cause hard-to-debug race conditions in critical sections that violate the contract between locks and their protected shared variables. This paper proposes new hardware support for enforcing isolation of critical section execution. It can detect and tolerate races, allowing programs to execute race-free. Our hardware scheme targets the existing large code base of lockedbased parallel programs written in type unsafe languages such as C and C++. Our approach works directly on unmodified executables. An evaluation of 13 programs from the SPLASH2 and PARSEC suites shows that the cost of the additional hardware and the impact on the overall execution time is minimal for these applications. Our mechanism is complementary to hardware transactional memory in that it uses similar structures but focuses on enhancing the reliability of existing lock-based programs.

show abstract

Healing data races on-the-fly

Cited by 50 publications

References 44 publications

Exception handlers for healing component-based systems

Exception handlers for healing component-based systems

A Uniform Classification of Common Concurrency Errors

Hardware support for enforcing isolation in lock-based parallel programs

Contact Info

Product

Resources

About