Worst-Case Memory Consumption Analysis for SCJ

Jeppe Lunde Andersen, Mikkel Todberg, Andreas Engelbredt Dalsgaard, Rene Rydhof Hansen

Research output: Contribution to book/anthology/report/conference proceedingArticle in proceedingResearchpeer-review

7 Citations (Scopus)

Abstract

Safety-Critical Java is designed to be used for safety-critical and hard real-time systems. To ensure predictable behaviour garbage collection has been replaced by a scope based memory model. This model currently requires bounds on memory usage of scopes to be specified by developers. These bounds have to be strict worst-case memory bounds to ensure correct behaviour of these systems. Currently, common methods are measurement based or by careful inspection of the applications Java bytecode. Not only is this a cumbersome approach it is also potentially unsafe. In this paper we present a worst-case memory consumption tool for Safety-Critical Java and evaluate it on existing usecases and a new usecase building on the Cubesat Space Protocol.
Original languageEnglish
Title of host publicationProceedings of the 11th International Workshop on Java Technologies for Real-time and Embedded Systems
Number of pages9
PublisherAssociation for Computing Machinery
Publication date2013
Pages2-10
ISBN (Print)978-1-4503-2166-2
DOIs
Publication statusPublished - 2013
EventThe 11th International Workshop on Java Technologies for Real-Time and Embedded Systems - Karlsruhe, Germany
Duration: 9 Oct 201310 Oct 2013
Conference number: 11

Workshop

WorkshopThe 11th International Workshop on Java Technologies for Real-Time and Embedded Systems
Number11
Country/TerritoryGermany
CityKarlsruhe
Period09/10/201310/10/2013
SeriesProceedings of the International Workshop of Java Technologies for Real-Time and Embedded Systems
ISSN2154-056X

Fingerprint

Dive into the research topics of 'Worst-Case Memory Consumption Analysis for SCJ'. Together they form a unique fingerprint.

Cite this