Cited by 509Software Engineering ResearchSoftware Testing and Debugging TechniquesSoftware Engineering Techniques and Practices

Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports

Zhou, Jian, Zhang, Hongyu, Lo, David·2012·2012 34th International Conference on Software Engineering (ICSE)

Abstract

For a large and evolving software system, the project team could receive a large number of bug reports. Locating the source code files that need to be changed in order to fix the bugs is a challenging task. Once a bug report is received, it is desirable to automatically point out to the files that developers should change in order to fix the bug. In this paper, we propose BugLocator, an information retrieval based method for locating the relevant files for fixing a bug. BugLocator ranks all files based on the textual similarity between the initial bug report and the source code using a revised Vector Space Model (rVSM), taking into consideration information about similar bugs that have been fixed before. We perform large-scale experiments on four open source projects to localize more than 3,000 bugs. The results show that BugLocator can effectively locate the files where the bugs should be fixed. For example, relevant buggy files for 62.60% Eclipse 3.1 bugs are ranked in the top ten among 12,863 files. Our experiments also show that BugLocator outperforms existing state-of-the-art bug localization methods.

Integrity signals

Registry

Crossref · 10.1109/icse.2012.6227210

Cites

36 of 36 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Cites

Flagged first, then by citations

2 of the 38 references couldn’t be matched to a known paper.

Cited by

Sorted by citations

Authors
Zhou, J., Zhang, H., & Lo, D.
Affiliations
  • Tsinghua University (CN)
  • Singapore Management University (SG)
Venue
2012 34th International Conference on Software Engineering (ICSE)
Publisher
IEEE
Published
2012-06
Pages
14-24
ISSN
0270-5257 (ISSN-L)
OpenAlex
W3149255455
Cited by
507
References
38
Citations by year
2026: 26 · 2025: 34 · 2024: 31 · 2023: 53 · 2022: 57 · 2021: 58 · 2020: 42 · 2019: 41 · 2018: 28 · 2017: 39 · 2016: 27 · 2015: 31 · 2014: 18 · 2013: 20 · 2012: 2
FWCI
17.86
Type
conference paper
Language
en
Open access
closed
Locations
ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion)
Funders
  • National Natural Science Foundation of China
  • Tsinghua University
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
bug localization, bug reports, information retrieval, text similarity, eclipses, open source software

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review