Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
frama-c
Commits
31bf9e82
Commit
31bf9e82
authored
4 years ago
by
Virgile Prevosto
Browse files
Options
Downloads
Patches
Plain Diff
[aorai] document -aorai-instrumentation-history and Frama_C_aorai_show_state
parent
f80cb52c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/aorai/main.tex
+18
-5
18 additions, 5 deletions
doc/aorai/main.tex
with
18 additions
and
5 deletions
doc/aorai/main.tex
+
18
−
5
View file @
31bf9e82
...
...
@@ -997,16 +997,27 @@ int main(int c) {
\label
{
FigGeneratedLoopInvariants
}
\end{figure}
\section
{
Interaction with
Annotated Files
}
\section
{
Analyzing
Annotated Files
with Eva or WP
}
\label
{
collaboration
}
Once the annotated file has been generated, it remains to verify that all the
annotations hold. This section describes briefly how this can be done and some
common issues that may arise during verification.
\aorai
tries to generate ACSL annotations that stay in the fragment
supported by Value Analysis, so that this plug-in might be used over the
generated code, but there is no guarantee that it will be able to establish
the validity of all annotations.
In addition to annotations,
\aorai
generates an implementation for the transition
functions, so that it is possible to use the Eva plug-in of Frama-C on the
instrumented code. However, there's no guarantee that Eva will be able to
perform an analysis that stays precise enough to verify that the automaton
always ends in an accepting state. Aoraï will set up automatically a certain number
of parameters in Eva to help make the analysis more precise, but,
in the case of deterministic automata it is also possible
to use option
\texttt
{
-aorai-instrumentation-history n
}
to have the instrumentation
retain the
\texttt
{
n
}
previous states of the automaton (in addition to the
current state), that will be used for splitting Eva's abstract states. Furthermore,
each time Eva encounters a call to the
built-in function
\texttt
{
Frama
\_
C
\_
show
\_
aorai
\_
state
}
, it will display the current
state (together with the previous ones up to
\texttt
{
-aorai
\-
instrumentation-history
}
).
If the function is called with some arguments, their abstract value will also be
displayed.
Another possibility is to use the deductive verification plug-in WP.
Note however that the generated annotations are not guaranteed to be complete,
...
...
@@ -1224,6 +1235,8 @@ The plug-in is composed of three parts:
\section
{
Recent updates
}
\subsection
{
Frama-C+dev
}
\begin{itemize}
\item
Documentation for option
\texttt
{
-aorai-instrumentation-history
}
and built-in
\texttt
{
Frama
\_
C
\_
show
\_
aorai
\_
state
}
\item
Aoraï does not generate a C file by default anymore, relying on
kernel options
\texttt
{
-print
}
and
\texttt
{
-ocode
}
for that, like all
plug-ins. Remove corresponding ad'hoc options.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment