2017
DOI: 10.1587/transinf.2017edr0004
|View full text |Cite
|
Sign up to set email alerts
|

Software Analysis Techniques for Detecting Data Race

Abstract: SUMMARYData races are a multithreading bug. They occur when at least two concurrent threads access a shared variable, and at least one access is a write, and the shared variable is not explicitly protected from simultaneous accesses of the threads. Data races are well-known to be hard to debug, mainly because the effect of the conflicting accesses depends on the interleaving of the thread executions. Hence there have been a multitude of research efforts on detecting data races through sophisticated techniques … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 58 publications
0
3
0
Order By: Relevance
“…Dynamic analysis gets more popularity in many applications, such as data race detection [12], [26]- [28], atomicity violation detection [29]- [31], record and replay systems [32]- [35]. Researchers have surveyed data race detection techniques from various views [36]- [38]. Generally, data race detection techniques are based on two models: locksets and happens-before relation.…”
Section: Related Workmentioning
confidence: 99%
“…Dynamic analysis gets more popularity in many applications, such as data race detection [12], [26]- [28], atomicity violation detection [29]- [31], record and replay systems [32]- [35]. Researchers have surveyed data race detection techniques from various views [36]- [38]. Generally, data race detection techniques are based on two models: locksets and happens-before relation.…”
Section: Related Workmentioning
confidence: 99%
“…Numerous works were conducted on detecting data races based on dynamic or static approaches [2] in the past few years. Dynamic detection examined the behavior of the source code by collecting variables and aliases at runtime [3].…”
Section: Introductionmentioning
confidence: 99%
“…Previous studies have proposed a lot of approaches to expose and detect all kinds of concurrency bugs [29], such as deadlocks [30,31], data races [32,33], atomicity violations [34,35], and order violations [36]. Also, the studies have obtained many excellent results.…”
Section: Introductionmentioning
confidence: 99%