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.
Proceedings of the International Workshop of Java Technologies for Real-time and Embedded Systems, 2013, p. 2-10
Main Research Area:
International Workshop of Java Technologies for Real-time and Embedded Systems. Proceedings
The 11th International Workshop on Java Technologies for Real-Time and Embedded SystemsInternational workshop on Java technologies for real-time and embedded systems, 2013