Software fault localization, the act of identifying the locations of faults in a program, is widely
recognized to be one of the most tedious, time consuming, and expensive-yet equally critical …

This chapter describes traditional and intuitive fault localization techniques, including
program logging, assertions, breakpoints, and profiling. Many advanced fault localization …

Researchers have argued that for failure to be observed the following three conditions must
be met: CR= the defect was reached; CI= the program has transitioned into an infectious …

We report on the application of Genetic Programming to Software Fault Localisation, a
problem in the area of Search-Based Software Engineering (SBSE). We give both empirical …

Software fault localization techniques typically rank program components, such as
statements or predicates, in descending order of their suspiciousness (likelihood of being …

Compiler bugs are extremely harmful, but are notoriously difficult to debug because compiler
bugs usually produce few debugging information. Given a bug-triggering test program for a …

Failed error propagation (FEP) is known to hamper software testing, yet it remains poorly
understood. We introduce an information theoretic formulation of FEP that is based on …

Trace data is critical for fault localization (FL) to analyze suspicious statements potentially
responsible for a failure. However, existing trace representation meets its bottleneck mainly …

Pure spectrum‐based fault localization (SBFL) is a well‐studied statistical debugging
technique that only takes a set of test cases (some failing and some passing) and their code …

Testing and debugging is the most expensive, error-prone phase in the software
development life cycle. Automated software fault localization can drastically improve the …