Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 332

The DOI matches its Crossref record; 47 of the 47 references it cites were found in a registry or an index.

History Driven Program Repair

Le, Xuan Bach D., Lo, David, Le Goues, Claire·2016·2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER)

Abstract

Effective automated program repair techniques have great potential to reduce the costs of debugging and maintenance. Previously proposed automated program repair (APR) techniques often follow a generate-and-validate and test-case-driven procedure: They first randomly generate a large pool of fix candidates and then exhaustively validate the quality of the candidates by testing them against existing or provided test suites. Unfortunately, many real-world bugs cannot be repaired by existing techniques even after more than 12 hours of computation in a multi-core cloud environment. More work is needed to advance the capabilities of modern APR techniques. We propose a new technique that utilizes the wealth of bug fixesacross projects in their development history to effectively guide and drive a programrepair process. Our main insight is that recurring bug fixes are common inreal-world applications, and that previously-appearing fix patterns canprovide useful guidance to an automated repair technique. Based on this insight, our technique first automaticallymines bug fix patterns from the history of many projects. We then employ existingmutation operators to generate fix candidates for a given buggy program. Candidates that match frequently occurring historical bug fixes are consideredmore likely to be relevant, and we thus give them priority inthe random search process. Finally, candidates thatpass all the previously failed test cases are recommended as likely fixes. We compare our technique against existinggenerate-and-validate and test-driven APR approaches using 90 bugs from 5 Javaprograms. The experiment results show that our technique can producegood-quality fixes for many more bugs as compared to the baselines, while beingreasonably computationally efficient: it takes less than 20minutes, on average, to correctly fix a bug.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1109/saner.2016.76

Cites

47 of 47 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 47 references

Research works printed but not linked: 8

  1. 10.1145/781147.781148 · doi:10.1145/781147.781148
  2. 10.1145/1250734.1250736 · doi:10.1145/1250734.1250736
  3. 10.1109/ISSRE.2015.7381836 · doi:10.1109/issre.2015.7381836
  4. britton, 2013, Reversible debugging software, Tech Rep
  5. 10.1137/S009753970241096X · doi:10.1137/s009753970241096x
  6. bradbury, 2010, Automatic repair of concurrency bugs, International Symposium on Search Based Software Engineering (SSBSE) fast abstract
  7. tassey, 2002, The economic impacts of inadequate infrastructure for software testing, National Institute of Standards and Technology RTI Project, 7007
  8. 10.1145/2771783.2771791 · DOI · Paper page

Cited by

See all 332

Metadata

Authors
Le, X. B. D., Lo, D., & Le Goues, C.
Venue
2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER)
Publisher
IEEE
Published
2016-03
Pages
213-224
OpenAlex
W2400994325
Cited by
332
References
47
FWCI
28.72
Type
conference paper
Language
en
Open access
closed

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

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: History Driven Program Repair. https://app.cochat.ai/papers/10.1109/saner.2016.76
The paper
Le, X. B. D., Lo, D., & Le Goues, C. (2016). History Driven Program Repair. 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER). https://doi.org/10.1109/saner.2016.76

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.