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
4790a86c
Commit
4790a86c
authored
2 years ago
by
David Bühler
Browse files
Options
Downloads
Patches
Plain Diff
[Eva] User manual: fixes description of a message in the ACSL FAQ.
parent
c8ce03d6
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/eva/main.tex
+6
-7
6 additions, 7 deletions
doc/eva/main.tex
with
6 additions
and
7 deletions
doc/eva/main.tex
+
6
−
7
View file @
4790a86c
...
...
@@ -6653,15 +6653,14 @@ value is saved in \texttt{old}'') and has been called with a null pointer.
In this case, the message can be safely ignored.
\paragraph
{
Cannot evaluate ACSL term, unsupported ACSL construct: [...]
}
This message can be emitted as a warning, or as a simple feedback message.
In the latter case, this is just a notification concerning the fact that
an analyzed specification is ``too complex'' for
\Eva
{}
to currently interpret
it, but unnecessary for the soundness of the analysis (otherwise it would have
been emitted as a warning).
This message indicates that a specification is ``too complex'' for
\Eva
{}
to
currently interpret it, and is ignored by the analysis:
\Eva
{}
cannot prove the specification, nor use it to improve its analysis.
However, this has no impact on the soundness of the analysis.
This often arrives when using Frama-C's libc specifications for functions in
\texttt
{
string.h
}
, because these functions include a logical axiomatization
that is useful for the
\textsf
{
WP
}
plug-in.
In this context, and without
the warning
, they can be safely ignored.
that is useful for the
\textsf
{
WP
}
plug-in.
In this context
, they can be safely ignored.
\end{document}
...
...
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