Sciweavers

22 search results - page 1 / 5
» Finding causes of program output with the Java Whyline
Sort
View
CHI
2009
ACM
14 years 4 months ago
Finding causes of program output with the Java Whyline
Debugging and diagnostic tools are some of the most important software development tools, but most expect developers choose the right code to inspect. Unfortunately, this rarely o...
Andrew Jensen Ko, Brad A. Myers
ICSE
2008
IEEE-ACM
14 years 5 months ago
Debugging reinvented: asking and answering why and why not questions about program behavior
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,...
Andrew Jensen Ko, Brad A. Myers
CORR
2010
Springer
143views Education» more  CORR 2010»
13 years 1 months ago
Cause Clue Clauses: Error Localization using Maximum Satisfiability
Much effort is spent everyday by programmers in trying to reduce long, failing execution traces to the cause of the error. We present a new algorithm for error cause localization ...
Manu Jose, Rupak Majumdar
ENTCS
2002
88views more  ENTCS 2002»
13 years 4 months ago
Testing Concurrent Java Programs using Randomized Scheduling
The difficulty of finding errors caused by unexpected interleavings of threads in concurrent programs is well known. Model checkers can pinpoint such errors and verify correctness...
Scott D. Stoller
SIGSOFT
2006
ACM
14 years 5 months ago
Finding failure-inducing changes in java programs using change classification
Testing and code editing are interleaved activities during program development. When tests fail unexpectedly, the changes that caused the failure(s) are not always easy to find. W...
Barbara G. Ryder, Frank Tip, Maximilian Störz...