Learning from mistakes: a comprehensive study on real world concurrency bug characteristics

By Shan Lu, Soyeon Park, Eunsoo Seo, Yuanyuan Zhou. International Conference on Architectural Support for Programming Languages and Operating Systems, 2008

1,014 citations recorded by the source corpus.

Subfields: Electrical and Electronic Engineering, Hardware and Architecture, Software

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

How researchers see this paper

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

In Electrical and Electronic Engineering

1. Shan Lu
2. Bowen Zhou
3. Yuanyuan Zhou
4. Li Zhang
5. Fei Wang
6. Seyit Ahmet Camtepe
7. Soyeon Park
8. Ji Liu

In Hardware and Architecture

1. Shan Lu
2. Sheng Wen
3. Yuanyuan Zhou
4. Rüdiger Kapitza
5. Peter R. Pietzuch
6. Anil Kurmus
7. Soyeon Park
8. Nico Weichbrodt

In Software

1. Shan Lu
2. Sheng Wen
3. Yuanyuan Zhou
4. Darko Marinov
5. Rüdiger Kapitza
6. Peter R. Pietzuch
7. Seyit Ahmet Camtepe
8. Anil Kurmus

Citations in the corpus

• AsyncShock: Exploiting Synchronisation Bugs in Intel SGX Enclaves (2016, background): “Synchronisation bugs are caused by the improper synchronised access of shared data by multiple threads, and previous studies have shown that they are a widespread issue [15, 27].”
• Finding and Reproducing Heisenbugs in Concurrent Programs (2008, neutral): “In the previous section, we described how fairness helps C HESS to focus only on fair schedules.”
• A comprehensive study on deep learning bug characteristics (2019, background): “patterns to explain the strong correlation of bugs in these libraries as bugs have strong relation to antipatterns [19]. There are some empirical studies focused on specific types of bugs. Lu et. al. [17] studied real-world concurrency bug characteristics. Gao et. al. [10] conducted an empirical stu”
• Fuzzing: A Survey for Roadmap (2022, background): “Generally, concurrency bugs are categorized into deadlock bugs and non-deadlock bugs [114].”
• CTrigger: exposing atomicity violation bugs from their hiding places (2009, background): “Among different types of concurrency bugs, atomicity violation bugs are one of the most common and important [13, 12 , 14, 25, 5]. Atomicity violation bugs (a realworld example is shown in Figure 1) widely exist because many programmers are used to sequential thinking and frequently assume code reg”
• An empirical analysis of flaky tests (2014, methodology): “In fact, bugs caused by asynchronous wait fall in a subcategory of concurrency bugs that Lu et al. [24] call “order violation” because the desired order of actions between multiple threads is not enforced.”
• GaDei: On Scale-Up Training as a Service for Deep Learning (2016, background): “It is difficult to detect, avoid and fix concurrency bugs[37].”