Yesterday, my program worked. Today, it does not. Why?
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.
| Zugehörige Institution(en) am KIT | Institut für Programmstrukturen und Datenorganisation (IPD) |
| Publikationstyp | Proceedingsbeitrag |
| Publikationsjahr | 1999 |
| Sprache | Englisch |
| Identifikator | ISBN: 978-3-540-66538-0 ISSN: 0302-9743 KITopen-ID: 1000017697 |
| Erschienen in | Software Engineering - ESEC/FSE 99. 7th European Software Engineering Conference Held Jointly with the 7th ACM SIGSOFT Symposium on the Foundations of Software Engineering Toulouse, France, September 6-10, 1999. Proceedings. Ed.: O. Nierstrasz |
| Verlag | Springer-Verlag |
| Seiten | 253 - 267 |
| Serie | Lecture notes in computer science ; 1687 |