Explaining bug provenance with trace witnesses
Authors: 
Jixiang Shen, Xi Wu, Neville Grech, Bernhard Scholz, Yannis SmaragdakisAuthors Info & Claims
Jixiang Shen, Xi Wu, Neville Grech, Bernhard Scholz, Yannis SmaragdakisAuthors Info & ClaimsPages 14 - 19
Abstract
Bug finders are mainstream tools used during software development that significantly improve the productivity of software engineers and lower maintenance costs. These tools search for software anomalies by scrutinising the program's code using static program analysis techniques, i.e., without executing the code. However, current bug finders do not explain why bugs were found, primarily due to coarse-grain abstractions that abstract away large portions of the operational semantics of programming languages. To further improve the utility of bug finders, it is paramount to explain reported bugs to the end-users.
In this work, we devise a new technique that produces a program trace for a reported bug giving insight into the root cause for the reported bug. For the generation of the program trace, we use an abstracted flow-based semantics for programs to overcome the undecidability of the problem. We simplify the semantic problem by mapping an input program with a reported bug to a Constant Copy Machine (CCM) for the trace construction. Using CCM the semantics of the program can be weakened, and thus bug provenance can be solved in polynomial time, producing a shortest trace in the process which gives the shortest explanation. The technique is reified in the bug tracing tool Digger and is evaluated on several open-source Java programs.
Supplementary Material
Video Presentation
- Download
- 52.27 MB
References
[1]
Cristina Cifuentes and Bernhard Scholz. 2008. Parfait - Designing a Scalable Bug Checker. In Scalable Program Analysis, Vol. 08161.
[2]
E. W. Dijkstra. 1959.
[3]
A Note on Two Problems in Connexion with Graphs. Numer. Math. 1, 1 (Dec. 1959), 269–271.
[4]
Jeanne Ferrante, Karl J. Ottenstein, and Joe D. Warren. 1987.
[5]
The Program Dependence Graph and Its Use in Optimization. ACM Trans. Program. Lang. Syst. 9, 3 (July 1987), 319–349.
[6]
Robert W. Floyd. 1962. Algorithm 97: Shortest Path. Commun. ACM 5, 6 (1962), 345.
[7]
William Landi. 1992.
[8]
Undecidability of Static Analysis. ACM Lett. Program. Lang. Syst. 1, 4 (Dec 1992), 323–337.
[9]
Ondrej Lhoták and Kwok-Chiang Andrew Chung. 2011.
[10]
Points-to Analysis with Efficient Strong Updates. SIGPLAN Not. 46 (2011), 3–16.
[11]
Roman Manevich, Manu Sridharan, Stephen Adams, Manuvir Das, and Zhe Yang. 2004.
[12]
PSE: Explaining Program Failures via Postmortem Static Analysis. SIGSOFT Softw. Eng. Notes 29, 6 (Oct 2004), 63–72.
[13]
David A. Patterson and John L. Hennessy. 1990.
[14]
Computer Architecture: A Quantitative Approach. Morgan Kaufmann Publishers Inc.
[15]
Bernhard Scholz, Herbert Jordan, Pavle Subotić, and Till Westmann. 2016. On Fast Large-scale Program Analysis in Datalog. In Proc. 25th International Conference on Compiler Construction. ACM, 196–206.
[16]
J. C. Shepherdson and H. E. Sturgis. 1963. Computability of Recursive Functions. J. ACM 10, 2 (April 1963), 217–255.
[17]
Yannis Smaragdakis and George Balatsouras. 2015. Pointer Analysis. Found. Trends Program. Lang. 2, 1 (Apr 2015), 1–69.
Index Terms
- Explaining bug provenance with trace witnesses
Recommendations
Reusing debugging knowledge via trace-based bug search
OOPSLA '12Some bugs, among the millions that exist, are similar to each other. One bug-fixing tactic is to search for similar bugs that have been reported and resolved in the past. A fix for a similar bug can help a developer understand a bug, or even directly ...
Reusing debugging knowledge via trace-based bug search
OOPSLA '12: Proceedings of the ACM international conference on Object oriented programming systems languages and applicationsSome bugs, among the millions that exist, are similar to each other. One bug-fixing tactic is to search for similar bugs that have been reported and resolved in the past. A fix for a similar bug can help a developer understand a bug, or even directly ...
Effective Bug Triage Based on Historical Bug-Fix Information
ISSRE '14: Proceedings of the 2014 IEEE 25th International Symposium on Software Reliability EngineeringFor complex and popular software, project teams could receive a large number of bug reports. It is often tedious and costly to manually assign these bug reports to developers who have the expertise to fix the bugs. Many bug triage techniques have been ...
Comments
Information & Contributors
Information
Published In
June 2020
19 pages
Copyright © 2020 ACM.
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]
Sponsors
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 15 June 2020
Check for updates
Author Tags
Qualifiers
- Research-article
Conference
PLDI '20
Sponsor:
Acceptance Rates
Overall Acceptance Rate 11 of 11 submissions, 100%
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 145Total Downloads
- Downloads (Last 12 months)8
- Downloads (Last 6 weeks)0
Reflects downloads up to 25 Feb 2025
Other Metrics
Citations
Cited By
View allView Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in