Answers are grounded in this paper and cite their sources.
Locating and fixing software faults is challenging. Traditional Spectrum-Based Fault Localization (SBFL) uses test coverage and failure data but often suffers from low accuracy due to a lack of semantic understanding of code. Deep-learning approaches can improve localization, but require extensive training data and computational resources. Recent Large Language Models (LLMs) offer a promising alternative with stronger code reasoning capabilities. However, existing LLM-based fault localization techniques still struggle at the repository level due to large context windows and positional bias, in which important debugging signals may be buried in large contexts. In this work, we introduce LLM4FL , a multi-LLM-agent-based fault localization technique designed to address these challenges. LLM4FL uses three specialized agents. The Context Extraction Agent divides and prioritizes covered methods into token-fitting groups using an order-aware strategy based on Ochiai suspiciousness scores. The Debugger Agent navigates the repository through graph-based retrieval to generate failure reasoning and rank suspicious methods. The Reviewer Agent then re-evaluates and re-ranks the results through iterative self-refinement and verbal reasoning. Evaluated on Defects4J, LLM4FL improves Top-1 accuracy over prior LLM-based approaches, including AutoFL and SoapFL , by 14.5% and 4.58%, respectively. Our ablation study further highlights the importance of LLM4FL's design choices, with failure reason generation improving Top-1 performance by 12.5% and order-aware division substantially improving localization accuracy by 18.07%.
No takes yet. Share an insight, caveat, or question.
Rafi et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: