Bug Finder and Code Prover report (-report-template)

Polyspace Bug Finder Summary: Number of results in the project. The results are summarized by file. The files that are partially analyzed because of compilation errors are listed in a separate table.

Code Metrics: Summary of the various code complexity metrics. For more information, see Code Metrics.

Coding Rules: Coding rule violations in the source code. For each rule violation, the report lists the:

Defects: Defects found in the source code. For each defect, the report lists the:

Configuration Settings: List of analysis options that Polyspace uses for analysis. If you configured your project for multitasking, this section also lists the Concurrency Modeling Summary. If your project has source files with compilation errors, these files are also listed.

If you check for coding rules, an additional Coding Rules Configuration section states the rules along with the information whether they were enabled or disabled.

Polyspace Bug Finder Summary: Number of results in the project. The results are summarized by file. The files that are partially analyzed because of compilation errors are listed in a separate table.

Code Metrics: Summary of the various code complexity metrics. For more information, see Code Metrics.

Coding Rules Summary: Coding rules along with number of violations.

Defect Summary: Defects that Polyspace Bug Finder™ looks for. For each defect, the report lists the:

Configuration Settings: List of analysis options that Polyspace uses for analysis. If you configured your project for multitasking, this section also lists the Concurrency Modeling Summary. For more information, see Complete List of Polyspace Bug Finder Analysis Engine Options. If your project has source files with compilation errors, these files are also listed.

If you check for coding rules, an additional Coding Rules Configuration section states the rules along with the information whether they were enabled or disabled.

Code Metrics Summary: Various quantities related to the source code. For more information, see Code Metrics.

Code Metrics Details: Various quantities related to the source code with the information broken down by file and function.

Configuration Settings: List of analysis options that Polyspace uses for analysis. If you configured your project for multitasking, this section also lists the Concurrency Modeling Summary. If your project has source files with compilation errors, these files are also listed.

If you check for coding rules, an additional Coding Rules Configuration section states the rules along with the information whether they were enabled or disabled.

Summary - Violations by File: Graph showing each file with number of rule violations.

Summary - Violations by Rule: Graph showing each rule with number of violations. If a rule is not enabled or not violated, it does not appear in the graph.

Summary for all Files: Table showing each file with number of rule violations.

Summary for Enabled Guidelines or Summary for Enabled Rules: Table showing each guideline or rule with number of violations.

Violations: Tables listing each rule violation, along with information such as ID, function name, severity, status, and so on. One table is created per file.

Information about whether the project satisfies quality objectives

Metrics for the whole project. For each metric, the report also lists the quality threshold and whether the metric satisfies this threshold.

Coding standard violations in the project. For each rule, the report lists the number of justified violations and whether the justifications satisfy Software Quality Objectives.

Summary - Violations by File: Graph showing each file with number of rule violations.

Summary - Violations by Rule: Graph showing each rule with number of violations. If a rule is not enabled or not violated, it does not appear in the graph.

Summary for all Files: Table showing each file with number of rule violations.

Summary for Enabled Guidelines or Summary for Enabled Rules: Table showing each guideline or rule with number of violations.

Violations: Tables listing each rule violation, along with information such as ID, function name, severity, status, and so on. One table is created per file.

Summary of verification results

Code metrics summary

Coding rules:

Run-time errors:

Global variable usage in code. See Global Variables.

Summary of results

Statistics about the code

Graphs showing distributions of checks per file

Variable name.

The entry for each variable is denoted by |.

Type of the variable.

Number of read and write operations on the variable.

Details of read and write operations. For each read or write operation, the table displays the following information:

Level of call hierarchy, where the function is called.

Each level is denoted by |. If a function call appears in the table as |||-> file_name.function_name, the function call occurs at the third level of the hierarchy. Beginning from main or an entry point, there are three function calls leading to the current call.

File containing the function call.

In addition, the line and column is also displayed.

File containing the function definition.

In addition, the line and column where the function definition begins is also displayed.

Information about whether the project satisfies quality objectives

Definite as well as possible run-time errors in the project. For each type of run-time error, the report lists the number of errors justified and whether the justifications satisfy quality objectives.