Iterative context bounding for systematic testing of multithreaded programs
By M. Musuvathi, Shaz Qadeer. ACM-SIGPLAN Symposium on Programming Language Design and Implementation, 2007
503 citations recorded by the source corpus.
Subfields: Computational Theory and Mathematics, Hardware and Architecture, Software
View Paper: https://www.semanticscholar.org/paper/6f8a16a73c576cba5b98a050190c2d75f6670358
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computational Theory and Mathematics
In Hardware and Architecture
In Software
- Claire Le Goues
- Westley Weimer
- Stephanie Forrest
- Koushik Sen
- Thanhvu Nguyen
- Martin C. Rinard
- Fan Long
- Andrea Arcuri
Citations in the corpus
- Learning from mistakes: a comprehensive study on real world concurrency bug characteristics (2008, unknown): “Specifically, how many threads, how many variables, and how many accesses are usually involved in a real world concurrency bug’s manifestation? Similar questions are also encountered in software verification and model checking [13, 28, 34] for concurrent programs.”
- Finding and Reproducing Heisenbugs in Concurrent Programs (2008, unknown): “The intuition behind this search strategy, called preemption bounding [32], is that many bugs are exposed in multithreaded programs by a few preemptions occurring in particular places in program execution.”
- Race directed random testing of concurrent programs (2008, background): “Static verification [4, 16, 28, 40, 8] and model checking [17, 29, 25, 27, 52, 31] or path-sensitive search of the state space is an alternative approach to finding bugs in concurrent programs.”
- Worst‐case execution time analysis for a Java processor (2010, unknown): “Some of the recent encouraging developments in this area include the CHESS tool of Microsoft Research [51, 53], the MODIST tool for verifying distributed systems by employing model-checking techniques in a lightweight manner [54], the Utah authors' group's tool Inspect for verifying C/Pthreads progr”
- GenProg: A Generic Method for Automatic Software Repair (2012, methodology): “This limitation could be mitigated by running each test case multiple times, incorporating scheduler constraints into the GP representation, and allowing a repair to contain both code changes and scheduling directives, or making multithreaded errors deterministic [43].”