2009
DOI: 10.1007/978-3-642-10452-7_18
|View full text |Cite
|
Sign up to set email alerts
|

Low-Level Code Verification Based on CSP Models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2010
2010
2016
2016

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 5 publications
0
5
0
Order By: Relevance
“…However, doing so would require extending Kothari's method with some kind of specification language for defining the properties, and with a mechanism for checking those specifications during symbolic execution. Kleine and Helke [2009] proposed using CSP to verify implementations of real-time multithreaded applications. Their approach appears to be similar to ours, in that it splits the CSP model into separate parts representing the application, the operating system, and the runtime environment.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, doing so would require extending Kothari's method with some kind of specification language for defining the properties, and with a mechanism for checking those specifications during symbolic execution. Kleine and Helke [2009] proposed using CSP to verify implementations of real-time multithreaded applications. Their approach appears to be similar to ours, in that it splits the CSP model into separate parts representing the application, the operating system, and the runtime environment.…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, the SyncExec process permits nesting of atomic blocks, although the nesting is necessarily restricted to a finite depth to allow model-checking. Following the approach used by Kleine and Helke [2009], we ensure the soundness of this abstraction by emitting the tos atomic err event to flag situations where the maximum depth is exceeded.…”
Section: Preemptionmentioning
confidence: 99%
“…These functions do not alter the behavior of the program but are commonly included for verification purposes. The concept of ghost functions and variables is explained in [13], for example. In order to keep the resulting models as small as possible in terms of memory consumption when analyzing them with FDR, the potentially infinite set of virtual SSA registers is mapped to a configurable number of registers when generating the CSP M model.…”
Section: Implementing Adaptive Systems Specified In Cspmentioning
confidence: 99%
“…Moreover, in previous work we have presented a methodology to construct concurrent implementations using CSP specifications [13,10]. Using these concepts we can obtain simulation environments and low-level implementations of adaptive systems from their CSP specifications.…”
Section: Introductionmentioning
confidence: 99%
“…An approach to extracting CSP models from LLVM compiler intermediate representation (IR) of C++ programs is presented ( (Kleine and Helke, 2009)). It divides the low-level representation of a concurrent system into three parts: an applicationspecific one, which describes thread behavior, a domain-specific one, which encapsulates low-level software concepts such as scheduling and stack frame, and a platformspecific one, which is the hardware model; a CSP model can be extracted from the application-specific part and then combined with (parameterized) CSP models for the other two parts to form a complete CSP model, which can be model checked by existing checkers for CSP such as FDR2 and ProB.…”
mentioning
confidence: 99%