Using Rescue Points to Navigate Software Recovery
Authors:
- 1 May 2007
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 273-280
Abstract
We present a new technique that enables software recovery in legacy applications by retrofitting exception-handling capabilities, error virtualization using rescue points. We introduce the idea of "rescue points" as program locations to which an application can recover its execution in the presence of failures. The use of rescue points reduces the chance of unanticipated execution paths thereby making recovery more robust by mimicking system behavior under controlled error conditions. These controlled error conditions can be thought of as a set erroneous inputs, like the ones used by most quality-assurance teams during software development, designed to stress-test an application. To discover rescue points applications are profiled and monitored during tests that bombard the program with bad/random inputs. The intuition is that by monitoring application behavior during these runs, we gain insight into how programmer-tested program points are used to propagate faults gracefully.Keywords
This publication has 12 references indexed in Scilit:
- Control-flow integrity2005
- Rx2005
- DART2005
- A Dynamic Technique for Eliminating Buffer Overflow Vulnerabilities (and Other Memory Errors)2005
- A Dynamic Mechanism for Recovering from Buffer Overflow Attacks2005
- Execution Generated Test Cases: How to Make Systems Code Crash Itself2005
- Y-branches: when you come to a fork in the road, take it2004
- Automatic detection and repair of errors in data structures2003
- Whither generic recovery from application faults? A fault study using open-source software2002
- An API for Runtime Code PatchingThe International Journal of High Performance Computing Applications, 2000