The following sections explain the different options you can use for codean..
The following options determine which type of data to collect.
Process and display static data.
Process and display dynamic data.
Process and display coverage data.
You can specify multiple options or none. If none are selected, than the default is to process all possible options, depending on whether the .analyze/type/latest file exists, where type can be static, dynamic, or coverage.
The following options determine the content of the text output of your results.
Display the full file's path name.
Display only the issues in the specified source file.
Display the specified number of lines of the source code.
Print version and exit without any further processing.
The following options determine which issues are reported in the results by filtering with the types of errors and warnings, the hash string, or the label name.
The error or warning type can be one of the following:
A three-letter error code or a three-letter warning code. For a list of possible errors and warnings, see Errors Analyzed by Code Analyzer.
MLK or mlk, for memory leaks.
ALL or all, for all warnings or errors.
If the error or warning is not specified, the default is all.
The filtering options are:
Show only errors of the specified error type.
Show only warnings of the specified warning type.
Do not show errors of the specified error type.
Do not show warnings of the specified warning type.
You can use hash strings to label issues. codean provides the following three labels: false_positive, verified, wont_be_fixed. For more information on using these labelling options, see Labelling Issues.
Display hash string associated with each issue.
Display only issues with the specified label.
Hide issues with the specified label.
Display only issues associated with the specified hash string hash. You can list more than one hash string.
You can save your latest results in a file, placed in a specific directory with specific tag names.
Save the latest reports.
When paired with –-save, names the saved copy with the tag name tag-name. If a saved copy has the same tag name, codean issues a warning message and then exits without overwriting the file. If no tag name is specified, codean checks the last modified time of the latest report of the executable and uses the time stamp as the tag name.
Overwrite the saved report with the same tag name.
Save the report to the directory directory.
The following options enable you to compare your results to a previously generated report.
Show only new issues. This option cannot be used with –-whatisfixed.
Show only fixed issues. This option cannot be used with –-whatisnew.
When paired with –-whatisnew or –-whatisfixed, uses the historic copy of the report with tag name tag-name to compare against newly generated report. If no tag name is specified, the latest report is compared against the last saved copy.
Must be paired with –-whatisnew or –-whatisfixed and must have a path name following it. This option specifies which file or directory to compare the new report against.
You can use the –-union option of codean to process multiple test reports to display, save, show new issues, or show fixed issues, of results from running discover on a test suite. For more information, see Using codean in Test Suites.
Present multiple dynamic reports. When specified with --save, --whatisnew, and --whatisfixed, it will save, show new issues, and show fixed issues of multiple dynamic reports respectively. The details of an issue that appear in multiple reports will be only displayed once.