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

Xiuhan Shi

dblp:332/6515 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2022
—ORCID · none

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

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

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
1 paper
Empirical software engineering · 61% Program verification · 30% Software testing · 9%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › mining software repositories
bug taxonomy
0.612022
Large-scale analysis of non-termination bugs in real-world OSS projects · ESEC/SIGSOFT FSE 2022
Empirical software engineering
mining software repositories
0.612022
Large-scale analysis of non-termination bugs in real-world OSS projects · ESEC/SIGSOFT FSE 2022
Program verification
termination analysis
0.612022
Large-scale analysis of non-termination bugs in real-world OSS projects · ESEC/SIGSOFT FSE 2022
Software testing › test infrastructure
benchmark construction
0.212022
Large-scale analysis of non-termination bugs in real-world OSS projects · ESEC/SIGSOFT FSE 2022

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

termination analysis tool evaluation · 0.6manual bug analysis · 0.6
YearPublicationVenuePosition
2022 Large-scale analysis of non-termination bugs in real-world OSS projects
abstract
Termination is a crucial program property. Non-termination bugs can be subtle to detect and may remain hidden for long before they take effect. Many real-world programs still suffer from vast consequences (e.g., no response) caused by non-termination bugs. As a classic problem, termination proving has been studied for many years. Many termination checking tools and techniques have been developed and demonstrated effectiveness on existing well-established benchmarks. However, the capability of these tools in finding practical non-termination bugs has yet to be tested on real-world projects. To fill in this gap, in this paper, we conducted the first large-scale empirical study of non-termination bugs in real-world OSS projects. Specifically, we first devoted substantial manual efforts in collecting and analyzing 445 non-termination bugs from 3,142 GitHub commits and provided a systematic classifi-cation of the bugs based on their root causes. We constructed a new benchmark set characterizing the real-world bugs with simplified programs, including a non-termination dataset with 56 real and reproducible non-termination bugs and a termination dataset with 58 fixed programs. With the constructed benchmark, we evaluated five state-of-the-art termination analysis tools. The results show that the capabilities of the tested tools to make correct verdicts have obviously dropped compared with the existing benchmarks. Meanwhile, we identified the challenges and limitations that these tools face by analyzing the root causes of their unhandled bugs. Fi-nally, we summarized the challenges and future research directions for detecting non-termination bugs in real-world projects.
Xiuhan Shi, Xiaofei Xie, Yi Li 0008, Yao Zhang 0019, Sen Chen 0001, Xiaohong Li 0001
ESEC/SIGSOFT FSE1