Debugging reinvented: asking and answering why and why not questions about program behavior

ABSTRACT

When software developers want to understand the reason for a program's behavior, they must translate their questions about the behavior into a series of questions about code, speculating about the causes in the process. The Whyline is a new kind of debugging tool that avoids such speculation by instead enabling developers to select a question about program output from a set of why did and why didn't questions derived from the program's code and execution. The tool then finds one or more possible explanations for the output in question, using a combination of static and dynamic slicing, precise call graphs, and new algorithms for determining potential sources of values and explanations for why a line of code was not reached. Evaluations of the tool on one task showed that novice programmers with the Whyline were twice as fast as expert programmers without it. The tool has the potential to simplify debugging in many software development contexts.

REFERENCES

• 1: Robin Abraham , Martin Erwig, Goal-Directed Debugging of Spreadsheets, Proceedings of the 2005 IEEE Symposium on Visual Languages and Human-Centric Computing, p.37-44, September 20-24, 2005 [doi>10.1109/VLHCC.2005.42]
• 2: Baowen Xu , Ju Qian , Xiaofang Zhang , Zhongqiang Wu , Lin Chen, A brief survey of program slicing, ACM SIGSOFT Software Engineering Notes, v.30 n.2, March 2005 [doi>10.1145/1050849.1050865]
• 3: James Clause , Alessandro Orso, A Technique for Enabling and Supporting Debugging of Field Failures, Proceedings of the 29th international conference on Software Engineering, p.261-270, May 20-26, 2007 [doi>10.1109/ICSE.2007.10]
• 4: Holger Cleve , Andreas Zeller, Locating causes of program failures, Proceedings of the 27th international conference on Software engineering, May 15-21, 2005, St. Louis, MO, USA [doi>10.1145/1062455.1062522]
• 5: Cooper K.D., Harvey T.J. & Kennedy K. (2001). A simple, fast dominance algorithm. Available at http://www.hipersoft.rice.edu/grads/publications/dom14.pdf.
• 6: Andrew David Eisenberg , Kris De Volder, Dynamic Feature Traces: Finding Features in Unfamiliar Code, Proceedings of the 21st IEEE International Conference on Software Maintenance, p.337-346, September 25-30, 2005 [doi>10.1109/ICSM.2005.42]
• 7: Andrew J. Ko , Robert DeLine , Gina Venolia, Information Needs in Collocated Software Development Teams, Proceedings of the 29th international conference on Software Engineering, p.344-353, May 20-26, 2007 [doi>10.1109/ICSE.2007.45]
• 8: Andrew J. Ko , Brad A. Myers, Designing the whyline: a debugging interface for asking questions about program behavior, Proceedings of the SIGCHI conference on Human factors in computing systems, p.151-158, April 24-29, 2004, Vienna, Austria [doi>10.1145/985692.985712]
• 9: Andrew J. Ko , Brad A. Myers , Duen Horng Chau, A Linguistic Analysis of How People Describe Software Problems, Proceedings of the Visual Languages and Human-Centric Computing, p.127-134, September 04-08, 2006 [doi>10.1109/VLHCC.2006.3]
• 10: Andrew J. Ko , Brad A. Myers , Michael J. Coblenz , Htet Htet Aung, An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks, IEEE Transactions on Software Engineering, v.32 n.12, p.971-987, December 2006 [doi>10.1109/TSE.2006.116]
• 11: Raimondas Lencevicius , Urs Hölzle , Ambuj K. Singh, Dynamic Query-Based Debugging of Object-Oriented Programs, Automated Software Engineering, v.10 n.1, p.39-74, January 2003 [doi>10.1023/A:1021816917888]
• 12: Lewis B. (2003). Debugging backwards in time, International Workshop on Automated Debugging, 225--235.
• 13: Ben Liblit , Mayur Naik , Alice X. Zheng , Alex Aiken , Michael I. Jordan, Scalable statistical bug isolation, Proceedings of the 2005 ACM SIGPLAN conference on Programming language design and implementation, June 12-15, 2005, Chicago, IL, USA
• 14: Brad A. Myers , David A. Weitzman , Andrew J. Ko , Duen H. Chau, Answering why and why not questions in user interfaces, Proceedings of the SIGCHI conference on Human Factors in computing systems, April 22-27, 2006, Montréal, Québec, Canada [doi>10.1145/1124772.1124832]
• 15: Alex Potanin , James Noble , Robert Biddle, Snapshot Query-Based Debugging, Proceedings of the 2004 Australian Software Engineering Conference (ASWEC'04), p.251, April 13-16, 2004
• 16: Manu Sridharan , Stephen J. Fink , Rastislav Bodik, Thin slicing, Proceedings of the 2007 ACM SIGPLAN conference on Programming language design and implementation, June 10-13, 2007, San Diego, California, USA
• 17: Tassey, G. (2002). The economic impacts of inadequate infrastructure for software testing. National Institute of Standards and Technology, RTI Project Number 7007.011, 2002.
• 18: David Ungar , Henry Lieberman , Christopher Fry, Debugging and the experience of immediacy, Communications of the ACM, v.40 n.4, p.38-43, April 1997 [doi>10.1145/248448.248457]
• 19: Tao Wang , Abhik Roychoudhury, Using Compressed Bytecode Traces for Slicing Java Programs, Proceedings of the 26th International Conference on Software Engineering, p.512-521, May 23-28, 2004
• 20: Xiangyu Zhang , Rajiv Gupta, Whole execution traces and their applications, ACM Transactions on Architecture and Code Optimization (TACO), v.2 n.3, p.301-334, September 2005 [doi>10.1145/1089008.1089012]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Debugging aids

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Tracing

  H. Information Systems
  H.5 INFORMATION INTERFACES AND PRESENTATION (I.7)
      H.5.2 User Interfaces (D.2.2, H.1.2, I.3.6)
          Subjects: User-centered design

General Terms:
Algorithms, Design, Human Factors, Performance, Reliability

Keywords:
whyline