Java concurrency

<p><strong>Data (External): </strong>"http://stap.sjtu.edu.cn/index.php?title=JaConTeBe#Searched_Bugs"</p> <p>Reference</p> <p>Studies who have been using the data (in any form) are required to include the following reference:</p> <p>@INPROCEEDINGS{7372007, author={Lin, Ziyi and Marinov, Darko and Zhong, Hao and Chen, Yuting and Zhao, Jianjun}, booktitle={Automated Software Engineering (ASE), 2015 30th IEEE/ACM International Conference on}, title={JaConTeBe: A Benchmark Suite of Real-World Java Concurrency Bugs (T)}, year={2015}, pages={178-189}, keywords={Benchmark testing;Computer bugs;Concurrent computing;Java;Open source software;System recovery;JaConTeBe;Java concurrency bugs;SIR;benchmark suite;evaluations}, doi={10.1109/ASE.2015.87}, month={Nov},}</p> <p>About the Data</p> <p>Overview of Data</p> <p>JaConTeBe is a benchmark suite for Java concurrency bugs. The initial version of JaConTeBe contains 47 confirmed, real-world concurrency bugs from 8. open-source projects. JaConTeBe is an ongoing work and the authors plan to collect more bugs in the future.</p> <p>Paper Abstract</p> <p>Researchers have proposed various approaches to detect concurrency bugs and improve multi-threaded programs, but performing evaluations of the effectiveness of these approaches still remains a substantial challenge. We survey the existing evaluations and find out that they often use code or bugs not representative of real world. To improve representativeness, we have prepared JaConTeBe, a benchmark suite of 47 confirmed concurrency bugs from 8 popular open-source projects, supplemented with test cases for reproducing buggy behaviors. Running three approaches on JaConTeBe shows that our benchmark suite confirms some limitations of the three approaches. We submitted JaConTeBe to the SIR repository (a software-artifact repository for rigorous controlled experiments), and it was included as a part of SIR.