From symptom to cause: localizing errors in counterexample traces

By Thomas Ball, Mayur Naik, Sriram K. Rajamani. 2003

353 citations recorded by the source corpus.

Subfields: Information Systems, Software

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

Citations in the corpus

Improving Robot Controller Transparency Through Autonomous Policy Explanation (2017, methodology): “In order to resolve issues stemming from logical errors, automated debugging methods have been introduced [4, 3, 34] that seek to identify faulty program statements.”
Debugging Machine Learning Tasks (2016, methodology): “[19] use a software model checker to generate correct and incorrect traces, and compute the diﬀerences between these traces to localize software defects.”
A genetic programming approach to automated software repair (2009, background): “, [6]) to help control the size of the weighted execution path.”
Fault localization with nearest neighbor queries (2003, background): “Existing work in model checking [2, 9] addresses this need for faults against a specification.”
Automated feedback generation for introductory programming assignments (2012, methodology): “o write the function computeDeriv that computes a list poly’ such that poly’ = n fi poly[i] j0 < i < len(poly)g if len(poly) > 1 [0:0] if len(poly) = 1 For example, if the input list poly is [2; 3;1;4](denoting f(x) = 4x3 + x2 3x+ 2), the computeDeriv function should return [ 03;2;12] (deno”
GenProg: A Generic Method for Automatic Software Repair (2012, background): “Trace localization [48], minimization [49], and explanation [50] projects also aim to elucidate faults and ease repairs.”
Automatically finding patches using genetic programming (2009, background): “Trace localization [8], minimization [15], and explanation [10] projects also aim to elucidate faults and ease repairs.”
Are automated debugging techniques actually helping programmers? (2011, background): “, [1, 8] and approaches based on model checking in general), statement coverage [11], and predicate values [17,19]—and in the specific type of mining performed on such information.”
SQLizer: query synthesis from natural language (2017, methodology): “Fault localization techniques [Ball et al. 2003; Groce and Visser 2003; Jones and Harrold 2005; Jones et al. 2002; Jose and Majumdar 2011a,b] aim to pinpoint a program expression that corresponds to the root cause of a bug.”
A Survey on Software Fault Localization (2016, methodology): “We now discuss model checking-based fault localization techniques that rely on the use of model checkers to locate bugs [44], [67], [133], [134], [136], [137], [138], [200].”
SherLog: error diagnosis by connecting clues from run-time logs (2010, background): “propose an algorithm to localize the root causes from model checking error traces [7].”
HDD: hierarchical delta debugging (2006, background): “suggest an approach to localize error causes [3].”
SLAM and Static Driver Verifier: Technology Transfer of Formal Methods inside Microsoft (2004, background): “Mayur Naik from Purdue University joined as a summer intern and worked on how to localize the cause of an error in an error trace produced by SLAM [BNR03].”
Thorough static analysis of device drivers (2006, background): “This harness leads to fewer false errors being reported but results in increased analysis times.”
Hoppity: Learning Graph Transformations to Detect and Fix Bugs in Programs (2020, background): “, 2018) or bug localization (Ball et al., 2003; Jose & Majumdar, 2011; Wang et al., 2019) techniques only solve a single task.”