Proceedings of the 12th Workshop on Formal Techniques for Java-Like Programs 2010
DOI: 10.1145/1924520.1924526
|View full text |Cite
|
Sign up to set email alerts
|

Prototyping a tool environment for run-time assertion checking in JML with communication histories

Abstract: In this paper we present prototype tool-support for the runtime assertion checking of the Java Modeling Language (JML) extended with communication histories specified by attribute grammars. Our tool suite integrates Rascal, a meta programming language and ANTLR, a popular parser generator. Rascal instantiates a generic model of history updates for a given Java program annotated with history specifications. ANTLR is used for the actual evaluation of history assertions.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 18 publications
0
6
0
Order By: Relevance
“…These sequences themselves are recorded by means of a fully automated instrumentation of the given program. This paper extends a previous workshop paper [5] as follows: It significantly extended the tool to a much larger part of Java (all features in table 1 are new, and more). The specification language is much more expressive by including assertions and conditional productions in attribute grammars.…”
Section: Introductionmentioning
confidence: 53%
“…These sequences themselves are recorded by means of a fully automated instrumentation of the given program. This paper extends a previous workshop paper [5] as follows: It significantly extended the tool to a much larger part of Java (all features in table 1 are new, and more). The specification language is much more expressive by including assertions and conditional productions in attribute grammars.…”
Section: Introductionmentioning
confidence: 53%
“…The well-known approach to alleviate such exposures is the introduction of ghost variables [6,7]; in section 4.1.4 we will show instead specifications based on the possible sequences of method calls -in line with [3], we believe that this is a more abstract style.…”
Section: Pol A1: Getsellercontract Returns Fresh Contractsmentioning
confidence: 99%
“…• we have permission on the val and next fields (line 14,15); and • we have conditional recursive access (lines [16][17][18][19][20][21][22] After we have finished the encoding of predicates, we will start working on the encoding of reentrant locks.…”
Section: Encoding Verification Problems In Chalicementioning
confidence: 99%
“…However, their histories keep track of communication events, i.e., a communication history, represented as a sequence of messages denoting events as object creation, method invocation or method completion. A prototype toolsupport for run-time checking of JML annotated code extended with communication histories has been developed by De Boer et al [17]. In contrast to this event-based history, our history is databased, which allows one to reason about the data elements that are logged in it.…”
Section: Concurrent Data Structures and Synchronisation Techniquesmentioning
confidence: 99%