Sciweavers

22 search results - page 3 / 5
» Finding causes of program output with the Java Whyline
Sort
View
ISSTA
2010
ACM
13 years 7 months ago
The Google FindBugs fixit
In May 2009, Google conducted a company wide FindBugs “fixit”. Hundreds of engineers reviewed thousands of FindBugs warnings, and fixed or filed reports against many of the...
Nathaniel Ayewah, William Pugh
OOPSLA
2004
Springer
13 years 10 months ago
Finding and preventing run-time error handling mistakes
It is difficult to write programs that behave correctly in the presence of run-time errors. Existing programming language features often provide poor support for executing clean-u...
Westley Weimer, George C. Necula
KBSE
2007
IEEE
13 years 11 months ago
Finding errors in components that exchange xml data
Two or more components (e.g., objects, modules, or programs) interoperate when they exchange data, such as XML data. Using Application Programming Interface (API) calls exported b...
Mark Grechanik
SIGSOFT
2010
ACM
13 years 3 months ago
An effective dynamic analysis for detecting generalized deadlocks
We present an effective dynamic analysis for finding a broad class of deadlocks, including the well-studied lock-only deadlocks as well as the less-studied, but no less widespread...
Pallavi Joshi, Mayur Naik, Koushik Sen, David Gay
ICSE
2007
IEEE-ACM
14 years 5 months ago
Exception-Chain Analysis: Revealing Exception Handling Architecture in Java Server Applications
Although it is common in large Java programs to rethrow exceptions, existing exception-flow analyses find only single exceptionflow links, thus are unable to identify multiple-lin...
Chen Fu, Barbara G. Ryder