An uncaught exception analysis for Java

Jo, Jang-Wu; Chang, Byeong-Mo; Yi, Kwangkeun; Choe, Kwang-Moo

doi:10.1016/s0164-1212(03)00057-8

Cited by 38 publications

(21 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many exception flow analyses augment the type system of the underlying programming language with information about the exceptions that can be thrown by a particular language construct [9,10,11,12,13,14,15,16]. The analyses differ in their representation of the inferred exception clauses, and the speed and precision of the analysis, but the principle is always the same.…”

Section: Related Workmentioning

confidence: 99%

Modular type checking of anchored exception declarations

Dooren

Jacobs

Joosen

2014

Science of Computer Programming

View full text Add to dashboard Cite

Checked exceptions improve the robustness of software, but they also decrease its adaptability because they must be propagated explicitly, and because they must often be handled even if they cannot be thrown. Anchored exception declarations solve both problems by allowing a method to declare its exceptional behavior in terms of other methods.The original type checking analyses for anchored exception declarations, however, are not modular. In this paper, we present algorithms for modular verification of soundness in an object-oriented language without parametric polymorphism.

show abstract

Section: Related Workmentioning

confidence: 99%

Modular type checking of anchored exception declarations

Dooren

Jacobs

Joosen

2014

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…EJFlow [11] enables reasoning about exception flow using architectural level exception ducts. Jex [33], and the works of Jo et al [18], Sinha et al [35] and Fu et al [13] propose global flow analyses for exceptions in Java. Leroy and Pessaux [27] propose a type based program analysis to estimate the set of uncaught exceptions in ML.…”

Section: Related Workmentioning

confidence: 99%

On exceptions, events and observer chains

Bagherzadeh

Rajan

Darvish

2013

Proceedings of the 12th Annual International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

Modular understanding of behaviors and flows of exceptions may help in their better use and handling. Such reasoning tasks about exceptions face unique challenges in event-based implicit invocation (II) languages that allow subjects to implicitly invoke observers, and run the observers in a chain. In this work, we illustrate these challenge in Ptolemy and propose Ptolemyχ that enables modular reasoning about behaviors and flows of exceptions for event announcement and handling. Ptolemyχ's exception-aware specification expressions and boundary exceptions limit the set of (un)checked exceptions of subjects and observers of an event. Exceptional postconditions specify the behaviors of these exceptions. Greybox specifications specify the flows of these exceptions among the observers in the chain. Ptolemyχ's type system and refinement rules enforce these specifications and thus enable its modular reasoning. We evaluate the utility of Ptolemyχ's exception flow reasoning by applying it to understand a set of aspect-oriented (AO) bug patterns. We also present Ptolemyχ's semantics including its sound static semantics.

show abstract

“…Type-based approaches to dealing with exception objects have also been explored before [14,15], in the context of a separate exception analysis (i.e., not jointly with a precise points-to analysis and not in comparison to an object-based exception representation).…”

Section: Related Workmentioning

confidence: 99%

Efficient and Effective Handling of Exceptions in Java Points-to Analysis

Kastrinis

Smaragdakis

2013

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract.A joint points-to and exception analysis has been shown to yield benefits in both precision and performance. Treating exceptions as regular objects, however, incurs significant and rather unexpected overhead. We show that in a typical joint analysis most of the objects computed to flow in and out of a method are due to exceptional control-flow and not normal call-return control-flow. For instance, a context-insensitive analysis of the Antlr benchmark from the DaCapo suite computes 4-5 times more objects going in or out of a method due to exceptional control-flow than due to normal control-flow. As a consequence, the analysis spends a large amount of its time considering exceptions.We show that the problem can be addressed both effectively and elegantly by coarsening the representation of exception objects. An interesting find is that, instead of recording each distinct exception object, we can collapse all exceptions of the same type, and use one representative object per type, to yield nearly identical precision (loss of less than 0.1%) but with a boost in performance of at least 50% for most analyses and benchmarks and large space savings (usually 40% or more).

show abstract

An uncaught exception analysis for Java

Cited by 38 publications

References 11 publications

Modular type checking of anchored exception declarations

Modular type checking of anchored exception declarations

On exceptions, events and observer chains

Efficient and Effective Handling of Exceptions in Java Points-to Analysis

Contact Info

Product

Resources

About