• Corpus ID: 236034383

Towards a Benchmark Set for Program Repair Based on Partial Fixes

@article{Beyer2021TowardsAB,
  title={Towards a Benchmark Set for Program Repair Based on Partial Fixes},
  author={Dirk Beyer and Lars Grunske and Thomas Lemberger and Minxing Tang},
  journal={ArXiv},
  year={2021},
  volume={abs/2107.08038}
}
Software bugs significantly contribute to software cost and increase the risk of system malfunctioning. In recent years, many automated program-repair approaches have been proposed to automatically fix undesired program behavior. Despite of their great success, specific problems such as fixing bugs with partial fixes still remain unresolved. A partial fix to a known software issue is a programmer’s failed attempt to fix the issue the first time. Even though it fails, this fix attempt still… 

Figures from this paper

TSSB-3M: Mining single statement bugs at massive scale

  • Cedric RichterH. Wehrheim
  • Computer Science
    2022 IEEE/ACM 19th International Conference on Mining Software Repositories (MSR)
  • 2022
TLDR
Two datasets to provide access to bug fix datasets of this scale are released, SSB-9M and TSSB-3M, which focuses on over 3M single statement bugs which can be fixed solely by a single statement change.

References

SHOWING 1-10 OF 18 REFERENCES

Concolic program repair

TLDR
An integrated approach for detecting and discarding overfitting patches via systematic co-exploration of the patch space and input space through concolic path exploration, which presents the viewpoint of gradual correctness - repair run over longer time leads to less overfitting fixes.

Has the bug really been fixed?

TLDR
A novel notion of distance-bounded weakest precondition is introduced as the basis for the developed practical techniques to compute the coverage and disruption of a fix, which formalizes two criteria to determine whether a fix resolves a bug.

How do fixes become bugs?

TLDR
A comprehensive characteristic study on incorrect bug-fixes from large operating system code bases including Linux, OpenSolaris, FreeBSD and also a mature commercial OS developed and evolved over the last 12 years, investigating not only themistake patterns during bug-fixing but also the possible human reasons in the development process when these incorrect bugs were introduced.

Automatic Software Repair: A Survey

TLDR
A new class of approaches, namely program repair techniques, whose key idea is to try to automatically repair software systems by producing an actual fix that can be validated by the testers before it is finally accepted, or that is adapted to properly fit the system.

Supplementary Bug Fixes vs. Re-opened Bugs

  • Le AnF. KhomhB. Adams
  • Computer Science
    2014 IEEE 14th International Working Conference on Source Code Analysis and Manipulation
  • 2014
TLDR
Predictive models for re-opened bugs are constructed using historical information about supplementary bug fixes with a precision between 72.2% and 97%, as well as a recall between 47.7% and 65.3%.

An empirical study of supplementary bug fixes

TLDR
This paper investigates a group of bugs that were fixed more than once in open source projects - those bugs whose initial patches were later considered incomplete and to which programmers applied supplementary patches.

Defects4J: a database of existing faults to enable controlled testing studies for Java programs

TLDR
Defects4J, a database and extensible framework providing real bugs to enable reproducible studies in software testing research, and provides a high-level interface to common tasks in softwareTesting research, making it easy to con- duct and reproduce empirical studies.

Recurring bug fixes in object-oriented programs

TLDR
Based on graph-based representation of object usages, this work has developed several techniques to identify code peers, recognize recurring bug fixes, and recommend changes for code units from the bug fixes of their peers.

Angelix: Scalable Multiline Program Patch Synthesis via Symbolic Analysis

TLDR
Angelix is a novel semantics- based repair method that scales up to programs of similar size as are handled by search-based repair tools such as GenProg and SPR, and is more scalable than previously proposed semantics based repair methods such as SemFix and DirectFix.

Predicting recurring crash stacks

  • Hyunmin SeoSunghun Kim
  • Computer Science
    2012 Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
  • 2012
TLDR
Evaluation using the real Firefox crash data shows that the approach yields reasonable accuracy in prediction of recurring crashes, and had the technique been deployed earlier, more than 2,225 crashes in Firefox 3.6 could have been avoided.