Home

About

Advanced Search

Browse by Discipline

Scientific Societies

E-print Alerts

Add E-prints

E-print Network
FAQHELPSITE MAPCONTACT US


  Advanced Search  

 
Debugging Reinvented: Asking and Answering Why and Why Not Questions about Program Behavior
 

Summary: Debugging Reinvented: Asking and Answering Why and
Why Not Questions about Program Behavior
Andrew J. Ko and Brad A. Myers
Human-Computer Interaction Institute
School of Computer Science, Carnegie Mellon University
5000 Forbes Avenue, Pittsburgh, PA 15213
{ajko, bam}@cs.cmu.edu
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

  

Source: Anderson, Richard - Department of Computer Science and Engineering, University of Washington at Seattle

 

Collections: Computer Technologies and Information Sciences