Self-stabilizing Java

Eom, Yong hun; Demsky, Brian

doi:10.1145/2254064.2254099

Cited by 15 publications

(7 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Unlike these tools, the goal of RCV is to repair the execution of the application, not the source code -continued execution with RCV can reduce or eliminate data losses in running applications. Self-Stabilizing Java: SJava [12] is a Java type system that enables the compiler to prove that the effects of any error will be flushed from the system state after a fixed number of iterations. Input Rectification and Filtering: Input rectification [18] empirically learns a set of input constraints from benign training inputs, then enforces learned constraints on incoming inputs to nullify potential errors.…”

Section: Related Workmentioning

confidence: 99%

Automatic runtime error repair and containment via recovery shepherding

Long¹,

Sidiroglou-Douskos²,

Rinard³

2014

Proceedings of the 35th ACM SIGPLAN Conference on Programming Language Design and Implementation

View full text Add to dashboard Cite

We present a system, RCV, for enabling software applications to survive divide-by-zero and null-dereference errors. RCV operates directly on off-the-shelf, production, stripped x86 binary executa-bles. RCV implements recovery shepherding, which attaches to the application process when an error occurs, repairs the execution, tracks the repair effects as the execution continues, contains the repair effects within the application process, and detaches from the process after all repair effects are flushed from the process state. RCV therefore incurs negligible overhead during the normal execution of the application. We evaluate RCV on all divide-by-zero and null-dereference errors available in the CVE database [2] from January 2011 to March 2013 that 1) provide publicly-available inputs that trigger the error which 2) we were able to use to trigger the reported error in our experimental environment. We collected a total of 18 errors in seven real world applications, Wireshark, the FreeType library , Claws Mail, LibreOffice, GIMP, the PHP interpreter, and Chromium. For 17 of the 18 errors, RCV enables the application to continue to execute to provide acceptable output and service to its users on the error-triggering inputs. For 13 of the 18 errors, the continued RCV execution eventually flushes all of the repair effects and RCV detaches to restore the application to full clean functionality. We perform a manual analysis of the source code relevant to our benchmark errors, which indicates that for 11 of the 18 errors the RCV and later patched versions produce identical or equivalent results on all inputs.

show abstract

Section: Related Workmentioning

confidence: 99%

Automatic runtime error repair and containment via recovery shepherding

Long¹,

Sidiroglou-Douskos²,

Rinard³

2014

Proceedings of the 35th ACM SIGPLAN Conference on Programming Language Design and Implementation

View full text Add to dashboard Cite

show abstract

“…SJava [23] is a Java type system that exploits common iterative structures in applications. When a developer writes program in SJava, the compiler can prove that the effects of any error will be flushed from the system state after a fixed number of iterations.…”

Section: Related Workmentioning

confidence: 99%

Automatic error elimination by horizontal code transfer across multiple applications

Sidiroglou-DouskosStelios

LahtinenEric

LongFan

et al. 2015

SIGPLAN Not.

View full text Add to dashboard Cite

We present Code Phage (CP), a system for automatically transferring correct code from donor applications into recipient applications that process the same inputs to successfully eliminate errors in the recipient. Experimental results using seven donor applications to eliminate ten errors in seven recipient applications highlight the ability of CP to transfer code across applications to eliminate out of bounds access, integer overflow, and divide by zero errors. Because CP works with binary donors with no need for source code or symbolic information, it supports a wide range of use cases. To the best of our knowledge, CP is the first system to automatically transfer code across multiple applications.

show abstract

“…Background on SJava This section reviews the key ideas behind checking selfstabilization [8]. The two key ideas are: (1) to use a type system to arrange the program's state into a lattice of locations and then check that information only flows down this lattice and (2) bound how long information can remain at any given location in the lattice before it is evicted.…”

Section: Contributionsmentioning

confidence: 99%

“…This earlier work does not check that the actual application is self-stabilizing. SJava is a type system and static analyses that together check that a Java program is self-stabilizing [8]. A barrier to the adoption of this work is that the technique requires additional type annotations.…”

Section: Robot Controllermentioning

confidence: 99%

See 1 more Smart Citation

Sinfer: Inferring information flow lattices for checking self-stabilization

Eom

Demsky

2013

2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE)

Self Cite

View full text Add to dashboard Cite

Self-stabilizing programs are guaranteed to recover from state corruption caused by software bugs or other events and eventually reach the correct state. Many real-world applications including embedded controllers and multimedia applications can be designed to make key components self-stabilizing.Type systems and static analyses can automatically check whether a program is self stabilizing. The existing approach for checking self-stabilization requires developers to manually annotate code. We present an annotation inference algorithm that automatically derives an initial set of annotations and therefore lowers the effort to build self-stabilizing systems. Our experience with the algorithm indicates that it effectively inferred annotations for our benchmarks.

show abstract

Self-stabilizing Java

Cited by 15 publications

References 25 publications

Automatic runtime error repair and containment via recovery shepherding

Automatic runtime error repair and containment via recovery shepherding

Automatic error elimination by horizontal code transfer across multiple applications

Sinfer: Inferring information flow lattices for checking self-stabilization

Contact Info

Product

Resources

About