VLDB 2026 Research / reviewers in the wild / expert
Gabriel Byman
dblp:362/3346
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2026
0009-0008-7639-6722ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 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 |
Debugging and program repair · 67% Software testing · 33% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair
fault localization |
1.0 | 1 | 2026 | OptRCA: A More Efficient and Accurate Approach for Automated Root Cause Analysis and Explanation · ACM Trans. Softw. Eng. Methodol. 2026 |
Software testing
fuzzing |
1.0 | 1 | 2026 | OptRCA: A More Efficient and Accurate Approach for Automated Root Cause Analysis and Explanation · ACM Trans. Softw. Eng. Methodol. 2026 |
Debugging and program repair
root cause analysis |
1.0 | 1 | 2026 | OptRCA: A More Efficient and Accurate Approach for Automated Root Cause Analysis and Explanation · ACM Trans. Softw. Eng. Methodol. 2026 |
Methods — techniques the papers use, named apart from their topics
reverse execution · 1.0hill-climbing retention · 1.0backward taint analysis · 1.0AFL crash mode · 1.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2026 | OptRCA: A More Efficient and Accurate Approach for Automated Root Cause Analysis and ExplanationabstractWith the development of automated software testing technology, software developers can get a large number of crash test cases in a short period of time. However, analyzing these crash test cases and finding their root cause is a time-consuming and labor-intensive task. Techniques based on reverse execution and backward taint analysis are proposed to locate the root cause, but can’t provide context information or explanation of the underlying fault. To address these two limitations, researchers have proposed an automated root cause analysis technique called AURORA. Although this technique provides powerful root cause analysis capabilities, it also have two obvious shortcomings. First, the results of root cause analysis are not accurate enough. Second, the efficiency of root cause analysis is not high enough. In order to improve these two shortcomings, we propose OptRCA, a more efficient and accurate approach for root cause analysis and explanation. Like AURORA’s fuzzing strategy, OptRCA is also designed based on AFL’s crash mode. The difference between them is mainly reflected in three points. First of all, the goal pursued by OptRCA is different from that of normal fuzzing technology. OptRCA pursues maximum correlation to ensure that as many crash test cases as possible are related to the same root cause. This test case with maximum correlation can greatly improve the accuracy of root cause analysis. Second, OptRCA proposed a more efficient non-crash test case retention strategy, which we named “Hill-Climbing Retention.” Using the hill-climbing retention method, OptRCA can obtain sufficient root cause information while retaining only a few non-crash test cases. Since the number of test cases is greatly reduced, the efficiency of OptRCA’s subsequent root cause analysis process is also greatly improved. In addition, OptRCA also optimizes the analysis formula to obtain more accurate analysis results. In the evaluation experimental results, OptRCA is significantly better than AURORA in terms of accuracy and efficiency. Quantitative analysis shows that OptRCA is 65% more accurate and 61% more efficient than AURORA. Jingquan Ge, Yaowen Zheng, Yuekang Li, Wei Ma 0014, Sheikh Mahbub Habib, Praveen Kakkolangara, Gabriel Byman, Yang Liu 0003 |
ACM Trans. Softw. Eng. Methodol. | 7 |