(Enter summary)
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 failureinducing
changes. Our delta debugging prototype tracked down a single failureinducing
change from 178,000 changed GDB lines within a few hours. (Update)
Context of citations to this paper: More
...on large projects is bug isolation. While we have not yet resorted to an automated defect isolation approach, e.g. delta debugging [19], we have used simple scripts to crudely isolate specific problems. Defect tracking is essential for large software development projects....
...the surface of debugging, verification and testing in this article. Other significant work can be found on automated debugging [33], coverage based testing techniques [34] performance testing and analysis [35] and concurrent and distributed testing [36] Testing and...
Cited by: More
Automated Debugging: Are We Close? - Zeller (2001)
(Correct)
Simplifying and Isolating Failure-Inducing Input - Zeller, Hildebrandt (2002)
(Correct)
Software Debugging, Testing, and Verification - Hailpern, Santhanam (2001)
(Correct)
Similar documents (at the sentence level):
79.4%: Yesterday, my program worked. Today, it does not. Why? - Zeller (1999)
(Correct)
Active bibliography (related documents): More All
0.4: Software Configuration Management: State of the Art, State of .. - Frühauf, Zeller
(Correct)
0.2: Isolating Failure-Inducing Input - Zeller (2001)
(Correct)
0.2: Isolating Failure-Inducing Thread Schedules - Choi, Zeller (2002)
(Correct)
Similar documents based on text: More All
1.0: DDD - A Free Graphical Front-End for UNIX Debuggers - Zeller, Lütkehaus (1995)
(Correct)
0.6: Visualizing Memory Graphs - Zimmermann, Zeller (2001)
(Correct)
0.6: Simplifying Failure-Inducing Input - Hildebrandt, Zeller (2000)
(Correct)
Related documents from co-citation: More All
2: The Mythical Man-Month (context) - Brooks - 1978
2: A Survey of Program Slicing Techniques
- Tip - 1995
BibTeX entry: (Update)
A. Zeller, "Yesterday, My Program Worked. Today, It Does Not. Why?" in Software Enginering -- ESEC/FSE '99, Lecture Notes in Computer Science Vol 1687, Springer Verlag, Sept. 1999. Also published as ACM SIGSOFT Software Engineering Notes, Vol. 24, No. 6, November 1999. http://citeseer.ist.psu.edu/zeller99yesterday.html More
@inproceedings{ zeller99yesterday,
author = "Andreas Zeller",
title = "Yesterday, My Program Worked. Today, It Does Not. Why?",
booktitle = "{ESEC} / {SIGSOFT} {FSE}",
pages = "253-267",
year = "1999",
url = "citeseer.ist.psu.edu/zeller99yesterday.html" }
Citations (may not include all citations):
296
Free Software Foundation (context) - STALLMAN, AND - 1998
48
The CM challenge: Configuration management that works (context) - LEBLANG - 1994
26
Unified versioning through feature logic
- ZELLER, AND - 1997
25
Program integration for languages with procedure calls
- BINKLEY, HORWITZ et al. - 1995
23
Semantics guided regression test cost reduction (context) - BINKLEY - 1997
12
DDD---A free graphical front-end for UNIX debuggers
- ZELLER, AND et al. - 1996
6
Versioning system models through description logic (context) - ZELLER - 1998
3
ACM Transactions on Software Engineering and Methodology (context) - TICHY - 1986
2
Regression containment through source code isolation (context) - NESS, AND - 1997
1
Computer Science Report (context) - ZELLER - 1999
Documents on the same site (http://www.infosun.fmi.uni-passau.de/st/papers/tr-99-01/):
Yesterday, my program worked. Today, it does not. Why? - Zeller (1999)
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC