Home

How did the failure come to be?

How did the failure come to be?
Free download from ACM
Related tools & artifacts:
Workshop Paper: CoCoS'17, October, 2017

Upon a program failure, programmers ask how the failure came to be. Modern debugging tools employ sophisticated mechanisms to help answering this question. These mechanisms embody a spectrum of contributions to program comprehension. In this paper, we study this spectrum with the goal of finding an optimal position. We define the optimal position as the set of techniques which tools can employ to efficiently answer this debugging question. Our position demands a big picture of a program execution, which is essential for better program comprehension. We demonstrate our position with two case studies. We envision that emerging debugging tools can benefit from taking this position to facilitate the debugging process.

@inproceedings{Azadmanesh:2017:DFC:3141842.3141845, author = {Azadmanesh, Mohammadreza and Hauswirth, Matthias}, title = {How Did the Failure Come to Be?}, booktitle = {Proceedings of the 2Nd ACM SIGPLAN International Workshop on Comprehension of Complex Systems}, series = {CoCoS 2017}, year = {2017}, isbn = {978-1-4503-5521-6}, location = {Vancouver, BC, Canada}, pages = {13--18}, numpages = {6}, url = {http://doi.acm.org/10.1145/3141842.3141845}, doi = {10.1145/3141842.3141845}, acmid = {3141845}, publisher = {ACM}, address = {New York, NY, USA}, keywords = {answer, debugging, question}, }