Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005. · 2005 · 116 citations · 15 references
ComputingComputer ScienceFault-tolerant ComputingFault-tolerant SystemsSoftware EngineeringDefect DetectionFailure AnalysisFailure DetectionFault DetectionRoot Cause AnalysisSoftware TestingAutomated Bug FindingDebugging TechniquesFailure Cause AnalysisFault Propagation AnalysisProgramming Software ErrorsSoftware Failure AnalysisSoftware Failure DetectionSoftware Fault Detection
Which is the defect that causes a software failure? By comparing the program states of a failing and a passing run, we can identify the state differences that cause the failure. However, these state differences can occur all over the program run. Therefore, we focus in space on those variables and values that are relevant for the failure, and in time on those moments where cause transitions occur - moments where new relevant variables begin being failure causes: "Initially, variable argc was 3; therefore, at shell-sort(), variable a[2] was 0, and therefore, the program failed." In our evaluation, cause transitions locate the failure-inducing defect twice as well as the best methods known so far.
15
Programmers use slices when debugging
Mark Weiser · Communications of the ACM · 1982 · 762 citations · Full text
Fault localization with nearest neighbor queries
M. Renieres, Steven P. Reiss · 2004 · 426 citations
PIE: a dynamic failure-based technique
J. Voas · IEEE Transactions on Software Engineering · 1992 · 399 citations