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
d962647b
Commit
d962647b
authored
4 years ago
by
Andre Maroneze
Browse files
Options
Downloads
Patches
Plain Diff
[Doc] add section about required build information
parent
b6f51172
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/userman/user-analysis-scripts.tex
+24
-0
24 additions, 0 deletions
doc/userman/user-analysis-scripts.tex
with
24 additions
and
0 deletions
doc/userman/user-analysis-scripts.tex
+
24
−
0
View file @
d962647b
...
...
@@ -73,6 +73,30 @@ re-running \texttt{make} should be enough to obtain a new result.
Section~
\ref
{
sec:using-generated-makefile
}
details usage of the Makefile
and presents an illustrative diagram.
\subsection
{
Necessary Build Information
}
\label
{
sec:necessary-build-information
}
For an analysis with
\FramaC
, besides the source code, the following pieces
of information are necessary:
\begin{description}
\item
[machdep]
: architectural information about system where the code will run:
integer type sizes, compiler, OS, etc. See section~
\ref
{
sec:normalize
}
for
more details.
\item
[preprocessing flags]
: options given to the C preprocessor, mainly
macros (
\texttt
{
-D
}
) and include directories (
\texttt
{
-I
}
).
\item
[list of sources]
: the actual list of source files that make a logical
unit (e.g. a test case or a whole program), without duplicate function
definitions.
\item
[main function]
: the function where the analysis will start; it is often
\texttt
{
main
}
, but not always. (
{
\em
Note:
\FramaC
itself thes not require
a
\texttt
{
main
}
function, but plug-ins such as
\texttt
{
Eva
}
do
}
.)
\end{description}
A project without such information is incomplete. In such cases, an alternative
workflow is necessary. The next section presents some possibilities to
retrieve such information.
\subsection
{
Possible Workflows in the Absence of Build Information
}
\label
{
alternative-workflows
}
...
...
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