Finding causes of program output with the Java Whyline
- 4 April 2009
- proceedings article
- Published by Association for Computing Machinery (ACM)
- p. 1569-1578
- https://doi.org/10.1145/1518701.1518942
Abstract
No abstract availableThis publication has 17 references indexed in Scilit:
- Debugging reinventedPublished by Association for Computing Machinery (ACM) ,2008
- Program comprehension as fact findingPublished by Association for Computing Machinery (ACM) ,2007
- Questions programmers ask during software evolution tasksPublished by Association for Computing Machinery (ACM) ,2006
- Answering why and why not questions in user interfacesPublished by Association for Computing Machinery (ACM) ,2006
- A brief survey of program slicingACM SIGSOFT Software Engineering Notes, 2005
- How effective developers investigate source code: an exploratory studyIEEE Transactions on Software Engineering, 2004
- An end-user tool for e-commerce debuggingPublished by Association for Computing Machinery (ACM) ,2003
- Isolating cause-effect chains from computer programsPublished by Association for Computing Machinery (ACM) ,2002
- Models of debuggingPublished by Elsevier ,2002
- Programmers use slices when debuggingCommunications of the ACM, 1982