scan-build-py-4.0 -V (return code: 127)
usage: scan-build-py-4.0 [-h] [--verbose] [--override-compiler]
[--intercept-first] [--cdb <file>] [--output <path>]
[--status-bugs] [--html-title <title>]
[--analyze-headers] [--plist | --plist-html]
[--keep-empty] [--no-failure-reports] [--stats]
[--internal-stats] [--maxloop <loop count>]
[--store <model>] [--constraints <model>]
[--use-analyzer <path>] [--use-cc <path>]
[--use-c++ <path>] [--analyzer-config <options>]
[--exclude <directory>] [--force-analyze-debug-code]
[--load-plugin <plugin library>]
[--enable-checker <checker name>]
[--disable-checker <checker name>] [--help-checkers]
[--help-checkers-verbose]
...
scan-build-py-4.0: error: unrecognized arguments: --version
scan-build-py-4.0 --help (return code: 127)
usage: scan-build-py-4.0 [-h] [--verbose] [--override-compiler]
[--intercept-first] [--cdb <file>] [--output <path>]
[--status-bugs] [--html-title <title>]
[--analyze-headers] [--plist | --plist-html]
[--keep-empty] [--no-failure-reports] [--stats]
[--internal-stats] [--maxloop <loop count>]
[--store <model>] [--constraints <model>]
[--use-analyzer <path>] [--use-cc <path>]
[--use-c++ <path>] [--analyzer-config <options>]
[--exclude <directory>] [--force-analyze-debug-code]
[--load-plugin <plugin library>]
[--enable-checker <checker name>]
[--disable-checker <checker name>] [--help-checkers]
[--help-checkers-verbose]
...
positional arguments:
build Command to run.
optional arguments:
-h, --help show this help message and exit
--verbose, -v Enable verbose output from 'scan-build-py-4.0'. A
second and third flag increases verbosity. (default:
0)
--override-compiler Always resort to the compiler wrapper even when better
interposition methods are available. (default: False)
--intercept-first Run the build commands only, build a compilation
database, then run the static analyzer afterwards.
Generally speaking it has better coverage on build
commands. With '--override-compiler' it use compiler
wrapper, but does not run the analyzer till the build
is finished. (default: False)
--cdb <file> The JSON compilation database. (default:
compile_commands.json)
--output <path>, -o <path>
Specifies the output directory for analyzer reports.
Subdirectory will be created if default directory is
targeted. (default: /tmp)
--status-bugs By default, the exit status of 'scan-build-py-4.0' is
the same as the executed build command. Specifying
this option causes the exit status of 'scan-build-
py-4.0' to be non zero if it found potential bugs and
zero otherwise. (default: False)
--html-title <title> Specify the title used on generated HTML pages. If not
specified, a default title will be used. (default:
None)
--analyze-headers Also analyze functions in #included files. By default,
such functions are skipped unless they are called by
functions within the main source file. (default:
False)
--plist, -plist This option outputs the results as a set of .plist
files. (default: html)
--plist-html, -plist-html
This option outputs the results as a set of .html and
.plist files. (default: html)
advanced options:
--keep-empty Don't remove the build results directory even if no
issues were reported. (default: False)
--no-failure-reports, -no-failure-reports
Do not create a 'failures' subdirectory that includes
analyzer crash reports and preprocessed source files.
(default: True)
--stats, -stats Generates visitation statistics for the project being
analyzed. (default: False)
--internal-stats Generate internal analyzer statistics. (default:
False)
--maxloop <loop count>, -maxloop <loop count>
Specifiy the number of times a block can be visited
before giving up. Increase for more comprehensive
coverage at a cost of speed. (default: None)
--store <model>, -store <model>
Specify the store model used by the analyzer. 'region'
specifies a field- sensitive store model. 'basic'
which is far less precise but can more quickly analyze
code. 'basic' was the default store model for
checker-0.221 and earlier. (default: None)
--constraints <model>, -constraints <model>
Specify the contraint engine used by the analyzer.
Specifying 'basic' uses a simpler, less powerful
constraint model used by checker-0.160 and earlier.
(default: None)
--use-analyzer <path>
'scan-build-py-4.0' uses the 'clang' executable
relative to itself for static analysis. One can
override this behavior with this option by using the
'clang' packaged with Xcode (on OS X) or from the
PATH. (default: clang)
--use-cc <path> When 'scan-build-py-4.0' analyzes a project by
interposing a "fake compiler", which executes a real
compiler for compilation and do other tasks (to run
the static analyzer or just record the compiler
invocation). Because of this interposing, 'scan-build-
py-4.0' does not know what compiler your project
normally uses. Instead, it simply overrides the CC
environment variable, and guesses your default
compiler. If you need 'scan-build-py-4.0' to use a
specific compiler for *compilation* then you can use
this option to specify a path to that compiler.
(default: cc)
--use-c++ <path> This is the same as "--use-cc" but for C++ code.
(default: c++)
--analyzer-config <options>, -analyzer-config <options>
Provide options to pass through to the analyzer's
-analyzer-config flag. Several options are separated
with comma: 'key1=val1,key2=val2' Available options:
stable-report-filename=true or false (default) Switch
the page naming to: report-<filename>-<function/method
name>-<id>.html instead of report-XXXXXX.html
(default: None)
--exclude <directory>
Do not run static analyzer against files found in this
directory. (You can specify this option multiple
times.) Could be usefull when project contains 3rd
party libraries. The directory path shall be absolute
path as file names in the compilation database.
(default: [])
--force-analyze-debug-code
Tells analyzer to enable assertions in code even if
they were disabled during compilation, enabling more
precise results. (default: False)
checker options:
--load-plugin <plugin library>, -load-plugin <plugin library>
Loading external checkers using the clang plugin
interface. (default: None)
--enable-checker <checker name>, -enable-checker <checker name>
Enable specific checker. (default: None)
--disable-checker <checker name>, -disable-checker <checker name>
Disable specific checker. (default: None)
--help-checkers A default group of checkers is run unless explicitly
disabled. Exactly which checkers constitute the
default group is a function of the operating system in
use. These can be printed with this flag. (default:
False)
--help-checkers-verbose
Print all available checkers and mark the enabled
ones. (default: False)