Finding and Reproducing Heisenbugs in Concurrent Programs

By Madanlal Musuvathi, Shaz Qadeer, Thomas Ball, Gérard Basler, Piramanayagam Arumuga Nainar, Iulian Neamtiu. USENIX Symposium on Operating Systems Design and Implementation, 2008

627 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/f68a1814799628d3ecbb2e46746d9c28ebe2c069

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

FastTrack: efficient and precise dynamic race detection (2009, methodology): “A variety of other approaches have also been developed, including model checking [7, 41, 25] and dataflow analysis [12, 15], as well as scalable whole-program analyses [26, 40].”
A Survey on Software Fault Localization (2016, methodology): “Another approach for bug localization in concurrent programs is to use model checking [60], [190], [261], [324].”
IronFleet: proving practical distributed systems correct (2015, methodology): “In principle, one can use model checking to reason about the correctness of both protocols [42, 60] and implementations [46, 47, 69].”
S2E: a platform for in-vivo multi-path analysis of software systems (2011, methodology): “Second, S(2)E employs virtualization to perform the desired analyses in vivo; this removes the need for the stubs or abstract models required by most state-of-the-art symbolic execution engines and model checkers [3, 11, 18, 28, 35].”
Structured Comparative Analysis of Systems Logs to Diagnose Performance Problems (2012, methodology): “Recent research on distributed systems has produced several methods to aid debugging of these complex systems, such as execution tracing [11, 14, 26], replay debugging [13], model checking [20,24], live property test-”