Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Arun K. Rajagopalan

dblp:167/7841 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 3 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Concurrent programming · 73% Program analysis · 27%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Concurrent programming
concurrency bugs
0.522016
Precise and maximal race detection from incomplete traces · OOPSLA 2016
RDIT: race detection from incomplete traces · ESEC/SIGSOFT FSE 2015
Concurrent programming › concurrency bug detection
data race detection
0.522016
Precise and maximal race detection from incomplete traces · OOPSLA 2016
RDIT: race detection from incomplete traces · ESEC/SIGSOFT FSE 2015
Concurrent programming › concurrency bug detection › data race detection
dynamic race detection
0.212016
Precise and maximal race detection from incomplete traces · OOPSLA 2016
Program analysis
dynamic analysis
0.212015
RDIT: race detection from incomplete traces · ESEC/SIGSOFT FSE 2015
Program analysis › dynamic analysis
happens-before analysis
0.212015
RDIT: race detection from incomplete traces · ESEC/SIGSOFT FSE 2015

Methods — techniques the papers use, named apart from their topics

maximal thread causality · 0.2logical constraints · 0.2barrierpair model · 0.2trace abstraction · 0.2happens-before algorithm · 0.2
YearPublicationVenuePosition
2017 What's the Optimal Performance of Precise Dynamic Race Detection? - A Redundancy Perspective
abstract
In a precise data race detector, a race is detected only if the execution exhibits a real race. In such tools, every memory access from each thread is typically checked by a happens-before algorithm. What’s the optimal runtime performance of such tools? In this paper, we identify that a significant percentage of memory access checks in real-world program executions are often redundant: removing these checks affects neither the precision nor the capability of race detection. We show that if all such redundant checks were eliminated with no cost, the optimal performance of a state-of-the-art dynamic race detector, FastTrack, could be improved by 90%, reducing its runtime overhead from 68X to 7X on a collection of CPU intensive benchmarks. We further develop a purely dynamic technique, ReX, that efficiently filters out redundant checks and apply it to FastTrack. With ReX, the runtime performance of FastTrack is improved by 31% on average.
Jeff Huang 0001, Arun K. Rajagopalan
ECOOP2
2016 Precise and maximal race detection from incomplete traces
abstract
We present RDIT, a novel dynamic technique to detect data races in multithreaded programs with incomplete trace information, i.e., in the presence of missing events. RDIT is both precise and maximal: it does not report any false alarms and it detects a maximal set of true traces from the observed incomplete trace. RDIT is underpinned by a sound BarrierPair model that abstracts away the missing events by capturing the invocation data of their enclosing methods. By making the least conservative abstraction that a missing method introduces synchronization only when it has a memory address in scope that overlaps with other events or other missing methods, and by formulating maximal thread causality as logical constraints, RDIT guarantees to precisely detect races with maximal capability. RDIT has been applied in seven real-world large concurrent systems and has detected dozens of true races with zero false alarms. Comparatively, existing algorithms such as Happens-Before, Causal- Precedes, and Maximal-Causality which are known to be precise all report many false alarms when missing synchronizations.
Jeff Huang 0001, Arun K. Rajagopalan
OOPSLA2
2015 RDIT: race detection from incomplete traces
abstract
We present RDIT, a novel dynamic algorithm to precisely detect data races in multi-threaded programs with incomplete trace information -- the presence of missing events. RDIT enhances the classical Happens-Before algorithm by relaxing the need to collect the full execution trace, while still guaranteeing full precision. The key idea behind RDIT is to abstract away the missing events by capturing the invocation data of the missing methods. This provides valuable information to approximate the possible synchronization behavior introduced by the missing events. By making the least conservative approximation that two missing methods introduce synchronization only when they access common data, RDIT guarantees to detect a maximal set of true races from the information available. We have conducted a preliminary study of RDIT on a real system and our results show that RDIT is promising; it detects no false positive when events are missed, whereas Happens-Before reports many.
Arun K. Rajagopalan, Jeff Huang 0001
ESEC/SIGSOFT FSE1