.trustinsoft/config.jsonfile for the branch that is going to be analyzed.
//ignores all characters until the end of line
/*ignores all characters until the next
nameto clearly identify the analysis in the result table in TrustInSoft CI
../can be annoying. To avoid such a task, the option
"prefix_path"can be used to prefix all paths by the given value:
int (int argc, char * argv), inputs can be given to the program with the
argcbound to k+1 and
argvpointing to a NULL-terminated array of pointers to strings
arg_kthe arguments given to
"val-args". The first character is used as separator to split the
"compilation-database"option should be added in your analysis configuration object with the paths to the compilation database file(s):
"compilation-database"option, the analyzer will scan all
compile_commands.jsonfiles located in this directory and sub-directories.
"cxx-std"option. If omitted, the default C++ standard used is
Bad libc callerror.
"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
Timeouterror. This limit can be increase up to 3 hours with the
Out of memoryerror, 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.