Static Memory and Execution Time Analysis of Embedded Code
Static Memory and Execution Time Analysis of Embedded Code
- New search for: Ferdinand, Christian
- New search for: Heckmann, Reinhold
- New search for: Ferdinand, Christian
- New search for: Heckmann, Reinhold
Failure of a safety-critical application on an embedded processor can lead to severe damage or even loss of life. Here we are concerned with two kinds of failure: stack overflow, which usually leads to run-time errors that are difficult to diagnose, and failure to meet deadlines, which is catastrophical for systems with hard real-time characteristics. Classical validation methods like code review and testing with repeated measurements require a lot of effort, are expensive, and do not really help in proving the absence of such errors. AbsInt's tools StackAnalyzer and aiT (timing analyzer) provide a solution to this problem. They use abstract interpretation as a formal method that allows to obtain statements valid for all program runs with all inputs.
Document information
Static Memory and Execution Time Analysis of Embedded Code
Sae Technical Papers
SAE 2006 World Congress & Exhibition ; 2006
2006-04-03
Conference paper
English
Similar titles
Static memory and execution time analysis of embedded code
| Automotive engineering | 2006
Worst-case execution time prediction by static program analysis
| Tema Archive | 2004
On static WCET analysis vs. run-time monitoring of execution time
| Tema Archive | 2004
A Hybrid Framework of Worst-Case Execution Time Analysis for Real-Time Embedded System Software
| British Library Conference Proceedings | 2005