REPFL is proposed, a novel LLM-based fault localisation approach that extends an existing coverage-based LLM localisation framework by replacing its reliance on coverage information with semantic reasoning over bug reports, retrieving and exploiting semantically related past issue reports alongside the current report.
Abstract
Continuous Integration (CI) facilitates a continuous development flow by automating build and test processes and providing rapid feedback. Such feedback often reports build or test failures, which indicate faults in the system under test (SUT) and initiate the debugging process, typically starting with fault localisation. Recent studies have employed Large Language Models (LLMs) to improve fault localisation by exploiting program and failure semantics. However, most existing approaches rely primarily on information from the current failure instance. In practice, developers frequently repeat similar mistakes; consequently, recently reported related issues and bug reports often describe recurring failures and may provide additional cues for localising new faults. In this work, we propose REPORTFL, a novel LLM-based fault localisation approach that extends an existing coverage-based LLM localisation framework by replacing its reliance on coverage information with semantic reasoning over bug reports, retrieving and exploiting semantically related past issue reports alongside the current report. Our approach aims to examine the usefulness of lexical and semantic context from current and relevant historical issues as an additional reasoning signal. REPORTFL assumes a realistic coverage-free CI scenario, in which only the failing test name and bug reports are available. An experimental evaluation on 302 real faults from open-source projects shows that, compared to the coverage-based LLM technique it builds upon, REPORTFL achieves comparable localisation performance when using GPT-3.5 and outperforms it when using a more capable model, GPT-4.1-mini, despite not relying on coverage information. Controlled ablations, retrieval-window analyses, and a random-report-selection baseline further show that semantically relevant historical issue reports can provide useful reasoning context for LLM-based fault localisation.
Automated bug reproduction from bug reports is a critical yet challenging step in software debugging. While LLM-based bug reproduction shows promise, its effectiveness is often hampered by insufficient contextual awareness of the relevant codebase and a tendency to produce invalid test cases. To address these limitatio...
Hao Ding, Yan-Jie Jiang, Yu-Xia Zhang et al.· Proceedings of the ACM on So...· 0 citations
CausalRepair is proposed, a conversation-driven APR framework based on minimal causal context, i.e., the essential dependencies required to explain a failure, outperforming state-of-the-art approaches such as ReinFix and TSAPR, while reducing the average repair cost to $0.029 per bug.
Lin-Hao Wu, Yi-Zhou Chen, Zhen Yang et al.· 0 citations
Large language models (LLMs) have shown promise for automated program repair, but it remains unclear which debugging signals are most useful and when additional context becomes distracting, costly, or ineffective. We present a controlled empirical study of LLM-based bug fixing on FIXEVAL, comparing three model families...
Dinesh Kumar Gummadavelli, Xian-Shan Qu, Xiao-Peng Li et al.· EAI Endorsed Transactions on...· 0 citations
A comprehensive empirical analysis of LLM-based APR techniques, focusing on how repair performance is shaped by bug complexity, fault localization, reasoning settings, and costs, reveals a nontrivial trade-off between repair effectiveness and computational cost.
Jun-Chi Liu, Ali Bigdeli, Roya Daneshi et al.· 1 citation
Analyzing crash-report bugs in large-scale industrial software systems requires substantial maintenance effort, particularly in production environments where developers must handle large volumes of crash reports and source code artifacts to localize and fix their root causes. While recent studies have shown that Large...
Marcos Medeiros, U. Kulesza, Christoph Treude et al.· 0 citations