The concurrent programming literature is rich with tools and techniques for data race
detection. Less, however, has been known about real-world, industry-scale deployment …

Data races are one of the most common and subtle causes of pernicious concurrency bugs.
Static techniques for preventing data races are overly conservative and do not scale well to …

Even though most data races are harmless, the harmful ones are at the heart of some of the
worst concurrency bugs. Alas, spotting just the harmful data races in programs is like finding …

Automatic static detection of data races is one of the most basic problems in reasoning about
concurrency. We present RacerD—a static program analysis for detecting data races in Java …

Go is a young programming language invented to build safe and efficient concurrent
programs. It provides goroutines as lightweight threads and channels for inter-goroutine …

Data races are subtle and difficult to detect errors that arise during concurrent program
execution. Traditional testing techniques fail to find these errors, but recent research has …

Data races indicate serious concurrency bugs such as order, atomicity, and sequential
consistency violations. Races are difficult to find and fix, often manifesting only after …

Data races often result in unexpected and erroneous behavior. In addition to causing data
corruption and leading programs to crash, the presence of data races complicates the …

Many concurrency bugs in multi-threaded programs are due to dataraces. There have been
many efforts to develop static and dynamic mechanisms to automatically find the data races …

To detect data races that harm production systems, program analysis must target production
runs. However, sound and precise data race detection adds too much run-time overhead for …