Sciweavers

180 search results - page 10 / 36
» Locating causes of program failures
Sort
View
ESEC
1999
Springer
14 years 1 months ago
Yesterday, My Program Worked. Today, It Does Not. Why?
Imagine some program and a number of changes. If none of these changes is applied (“yesterday”), the program works. If all changes are applied (“today”), the program does n...
Andreas Zeller
ISSTA
2000
ACM
14 years 1 months ago
Simplifying failure-inducing input
Given some test case, a program fails. Which part of the test case is responsible for the particular failure? We show how our delta debugging algorithm generalizes and simplifies...
Ralf Hildebrandt, Andreas Zeller
SIGSOFT
2006
ACM
14 years 9 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...
ASPLOS
2011
ACM
13 years 11 days ago
ConSeq: detecting concurrency bugs through sequential errors
Concurrency bugs are caused by non-deterministic interleavings between shared memory accesses. Their effects propagate through data and control dependences until they cause softwa...
Wei Zhang, Junghee Lim, Ramya Olichandran, Joel Sc...
EUROSYS
2009
ACM
14 years 5 months ago
First-aid: surviving and preventing memory management bugs during production runs
Memory bugs in C/C++ programs severely affect system availability and security. This paper presents First-Aid, a lightweight runtime system that survives software failures caused ...
Qi Gao, Wenbin Zhang, Yan Tang, Feng Qin