Residual Investigation Predictive and Precise Bug Detection

• Published in: ACM transactions on software engineering and methodology Vol. 24; no. 2; pp. 1 - 32
• Main Authors: Li, Kaituo, Reichenbach, Christoph, Csallner, Christoph, Smaragdakis, Yannis
• Format: Journal Article
• Language: English
• Published: 01.12.2014
• Subjects: Analyzers; Dynamic tests; Dynamics; Error analysis; Faults; Reporting; Running; Static code analysis; Warning
• ISSN: 1049-331X; 1557-7392
• DOI: 10.1145/2656201

We introduce the concept of residual investigation for program analysis. A residual investigation is a dynamic check installed as a result of running a static analysis that reports a possible program error. The purpose is to observe conditions that indicate whether the statically predicted program fault is likely to be realizable and relevant. The key feature of a residual investigation is that it has to be much more precise (i.e., with fewer false warnings) than the static analysis alone, yet significantly more general (i.e., reporting more errors) than the dynamic tests in the program's test suite that are pertinent to the statically reported error. That is, good residual investigations encode dynamic conditions that, when considered in conjunction with the static error report, increase confidence in the existence or severity of an error without needing to directly observe a fault resulting from the error. We enhance the static analyzer FindBugs with several residual investigations appropriately tuned to the static error patterns in FindBugs, and apply it to nine large open-source systems and their native test suites. The result is an analysis with a low occurrence of false warnings (false positives) while reporting several actual errors that would not have been detected by mere execution of a program's test suite.