PLDI '90 Proceedings of the ACM SIGPLAN 1990 conference on Programming language design and implementation
Dynamic slicing of computer programs
Journal of Systems and Software
Automatic isolation of compiler errors
ACM Transactions on Programming Languages and Systems (TOPLAS)
A new model of program dependences for reverse engineering
SIGSOFT '94 Proceedings of the 2nd ACM SIGSOFT symposium on Foundations of software engineering
An efficient relevant slicing method for debugging
ESEC/FSE-7 Proceedings of the 7th European software engineering conference held jointly with the 7th ACM SIGSOFT international symposium on Foundations of software engineering
Which pointer analysis should I use?
Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis
Programmers use slices when debugging
Communications of the ACM
Algorithm 457: finding all cliques of an undirected graph
Communications of the ACM
Dynamically Discovering Likely Program Invariants to Support Program Evolution
IEEE Transactions on Software Engineering - Special issue on 1999 international conference on software engineering
Change impact analysis for object-oriented programs
PASTE '01 Proceedings of the 2001 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Simplifying and Isolating Failure-Inducing Input
IEEE Transactions on Software Engineering
Tracking down software bugs using automatic anomaly detection
Proceedings of the 24th International Conference on Software Engineering
Visualization of test information to assist fault localization
Proceedings of the 24th International Conference on Software Engineering
Revised Lectures on Software Visualization, International Seminar
Algorithmic program debugging
Error traces in model-based debugging of hardware description languages
Proceedings of the sixth international symposium on Automated analysis-driven debugging
Lightweight bug localization with AMPLE
Proceedings of the sixth international symposium on Automated analysis-driven debugging
Proceedings of the 2007 ACM SIGPLAN conference on Programming language design and implementation
Using a pilot study to derive a GUI model for automated testing
ACM Transactions on Software Engineering and Methodology (TOSEM)
Property Patterns for Runtime Monitoring of Web Service Conversations
Runtime Verification
AVA: automated interpretation of dynamically detected anomalies
Proceedings of the eighteenth international symposium on Software testing and analysis
Is non-parametric hypothesis testing model robust for statistical fault localization?
Information and Software Technology
Evidence-based validation and improvement of electronic health record systems
Proceedings of the FSE/SDP workshop on Future of software engineering research
Locating failure-inducing environment changes
Proceedings of the 10th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools
Fault localization for data-centric programs
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Is text search an effective approach for fault localization: a practitioners perspective
Proceedings of the 3rd annual conference on Systems, programming, and applications: software for humanity
Hi-index | 0.01 |
Consider the execution of a failing program as a sequence of program states. Each state induces the following state, up to the failure. Which variables and values of a program state are relevant for the failure? We show how the Delta Debugging algorithm isolates the relevant variables and values by systematically narrowing the state difference between a passing run and a failing run--by assessing the outcome of altered executions to determine wether a change in the program state makes a difference in the test outcome. Applying Delta Debugging to multiple states of the program automatically reveals the cause-effect chain of the failure--that is, the variables and values that caused the failure.In a case study, our prototype implementation successfully isolated the cause-effect chain for a failure of the GNU C compiler: "Initially, the C program to be compiled contained an addition of 1.0; this caused an addition operator in the intermediate RTL representation; this caused a cycle in the RTL tree--and this caused the compiler to crash."