Yesterday, my program worked. Today, it does not. Why?
Author:
Open Access
- 1 October 1999
- journal article
- conference paper
- Published by Association for Computing Machinery (ACM) in ACM SIGSOFT Software Engineering Notes
- Vol. 24 (6) , 253-267
Abstract
Imagine some program and a number of changes. If none of these changes is applied (“yesterday”), the program works. If all changes are applied (“today”), the program does not work. Which change is responsible for the failure? We present an efficient algorithm that determines the minimal set of failure-inducing changes. Our delta debugging prototype tracked down a single failure-inducing change from 178,000 changed GDB lines within a few hours.Keywords
This publication has 5 references indexed in Scilit:
- Unified versioning through feature logicACM Transactions on Software Engineering and Methodology, 1997
- Semantics guided regression test cost reductionIEEE Transactions on Software Engineering, 1997
- DDD—a free graphical front-end for UNIX debuggersACM SIGPLAN Notices, 1996
- Program integration for languages with procedure callsACM Transactions on Software Engineering and Methodology, 1995
- Smart recompilationACM Transactions on Programming Languages and Systems, 1986