mixxxxa/PVS-Studio scan example
Easy way to configure PVS-Studio analyzer on GitHub
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| file-to-analyze | File to analyze (Compile Commands Database or trace-file) | yes | — |
| analysis-mode | The group of warnings that will be activated during analysis. Several values must be separated by ';', e.g. 'GA;OP;64' | no | GA;OP |
| output-format | Render types for output. Avaliable formats can be found in documentation. | yes | — |
| output-file | Output file. | yes | — |
| license-file | PVS-Studio license file | no | "" |
| source-tree-root | Replace absolute paths in report with relative paths | no | "" |
| parallel | Allow to run N PVS-Studio analyzers at once | no | 0 |
| excluded-dirs | Excludes from the report all warnings issued in certain files (wildcards supported). Several values must be separated by semicolon or new line, e.g. 'C:\dev\project\thirdparty;C:\dev\project\libs' | no | "" |
| suppress-files | Path to suppress files. | no | "" |
| rules-configs | Paths to the diagnostics configuration file (.pvsconfig) or to the directory containing configuration files | no | "" |
| additional-args | Additional args passed to analyzer. See documentation for more information. | no | "" |
Outputs
| name | description |
|---|---|
| report | Path to ready-to-use report in a specified format |
| raw-report | Path to raw analyzer report for further conversion and processing |