Build configuration
section:.trustinsoft/config.json
file for the branch that is going to be analyzed..trustinsoft/config.json
file during the Build preparation stage. //
ignores all characters until the end of line/*
ignores all characters until the next */
.c
or .cpp
files),
before any closing bracket }
or ]
. Otherwise it will lead to a syntax error of the JSON format.cpp-extra-args
orcxx-cpp-extra-args
can be omitted if the files do not need any particular pre-processing options.name
to clearly identify the analysis in the result table in TrustInSoft CImachdep
); if omitted, the default one is "gcc_x86_32"
(see also the list of Supported architecture)main
function.trustinsoft
.../
can be annoying. To avoid such a task, the option "prefix_path"
can be used to prefix all paths by the given value:"prefix_path"
option can also be used with a Global configuration if all your sources files are located in a same sub-directory.int (int argc, char * argv[])
, inputs can be given to the program with the "val-args"
option.argc
bound to k+1 and argv
pointing to a NULL-terminated array of pointers to strings program
, arg_1
, …, arg_k
with arg_1
, ..., arg_k
the arguments given to "val-args"
. The first character is used as separator to split the arg_k
arguments.argv[0]
is set by default to program
. This value can be changed with the "val-program-name"
option.int (int argc, char * argv[])
, then it is not possible to given an input with "val-args"
. In this case, it is recommended to use a test driver function (a function written only for a test purpose) which directly calls your function with the wanted input and to use the new test driver function as the entry point for the analysis."cpp-extra-args"
and "cxx-cpp-extra-args"
options to deduce the preprocessing options to use for the analyzed source files."compilation-database"
option should be added in your analysis configuration object with the paths to the compilation database file(s):"cpp-extra-args"
or "cxx-cpp-extra-args"
options are given in addition of the "compilation-database"
, these options are concatenated to the preprocessing command line (used by TrustInSoft Analyzer to parse the source files) after the preprocessing options extracted from the compilation database."compilation-database"
option, the analyzer will scan all compile_commands.json
files located in this directory and sub-directories."cxx-std"
option. If omitted, the default C++ standard used is c++11
.c++03
, c++0x
, c++11
, c++14
, c++17
, c++1y
, c++1z
, c++20
, c++2a
, c++98
, gnu++03
, gnu++0x
, gnu++11
, gnu++14
, gnu++17
, gnu++1y
, gnu++1z
, gnu++20
, gnu++2a
, gnu++98
.1
by default."address-alignment"
option:Bad libc call
error."filesystem"
option which contains a list of "files"
. Each file should indicate its "name"
used by the program and its associated file "from"
the real file system. The contents of the "name"
file during the analysis will be mapped to the one of the real "from"
file, allowing a deterministic behavior of functions operating on files (such as fgetc
, fread
, ...)."name"
needs to be exactly the same one used inside the program to open the file. Otherwise the file will not be correctly found and mapped to the "from"
file of the virtual file system.Timeout
error. This limit can be increase up to 3 hours with the "val-timeout"
option.Out of memory
error, it is possible to use the "no-results"
option to force TrustInSoft CI Analyzer to not keep results of the analysis in its memory. As a side effect, the "no-results"
can also slightly make the analysis faster."no-results"
option, the analysis may no longer hit the memory limit. However you will no longer be able to Inspect the result with the Graphical User Interface of TrustInSoft CI Analyzer.