Review Code Prover Results
R2026bAfter analysis, review results in the Polyspace Access™ user interface. You can do one of the following:
Start reviewing results immediately in your web browser.
Create and enforce authorization policies for project reviews.
Apply a result management strategy to narrow down the scope of your review, and then review your results.
Polyspace Code Prover checks C/C++ code for run-time errors. Check results appear in one of these colors:
Red (proven error)
Orange (unproven but possible error)
Green (proven absence of error)
For more details, see Code Prover Result and Source Code Colors (Polyspace Code Prover).
To review a result, trace back from the immediate location of the issue to previous related lines. The Polyspace Access web interface provide various conveniences such as range tooltips, function call hierarchy, and other navigation aids to help you with the traceback. Use these tools to locate the root cause of an issue and implement a fix. To understand what to look for when reviewing a particular type of check, see Reviewing Code Prover Run-Time Checks (Polyspace Code Prover).
Once you understand the root cause of a Polyspace finding, you can fix your code. Otherwise, add review information to the Polyspace result to mark it for fixing later or to justify the result. You can use the review information to keep track of your review progress and avoid reviewing the same finding twice.
If you add review information to your results in the Polyspace Access web interface, they carry over to results uploaded to the same project. If you add the same information as comments to your code (annotate), they carry over to any subsequent analysis of the code, whether in the same project or not. You can also hide results using code annotations.
System Commands
Topics
Getting Started
- Interpret Code Prover Results in Polyspace Access Web Interface
Interpret result details message, find root of result.
- Code Prover Result and Source Code Colors (Polyspace Code Prover)
- Reviewing Code Prover Run-Time Checks (Polyspace Code Prover)
- Polyspace Results in Lines Containing Macros (Polyspace Code Prover)
- Compare Results in Polyspace Access Project to Previous Runs
View results from previous project runs and compare them to later runs.
Code Prover Analysis
- Code Prover Analysis Following Red and Orange Checks (Polyspace Code Prover)
Learn how an operation containing a run-time error affects verification of subsequent code.
- Order of Code Prover Run-Time Checks (Polyspace Code Prover)
- Variable Ranges in Source Code Tooltips After Code Prover Analysis (Polyspace Code Prover)
Learn why Code Prover reports ranges on variables, and why certain ranges can be narrower than expected. - Orange Checks in Polyspace Code Prover (Polyspace Code Prover)
Learn why the verification cannot prove the presence or absence of an error for certain operations and why you must review the operations.
- Managing Orange Checks in Polyspace Code Prover (Polyspace Code Prover)
- Critical Orange Checks in Polyspace Code Prover (Polyspace Code Prover)
- Reduce Orange Checks in Polyspace Code Prover (Polyspace Code Prover)
Polyspace Access Dashboard View
- Dashboard in Polyspace Access Web Interface
See an overview of project results in graphical format, for instance, coding standard findings distribution by status. - Monitor Code Quality Using Quality Objectives Dashboard in Polyspace Access
Monitor the quality of your code and create custom quality objectives definitions.
- Code Metrics Dashboard in Polyspace Access Web Interface
See a summary of your code metrics and pass/fail criteria.
Add Review Information to Results
- Address Results in Polyspace Access Through Bug Fixes or Justifications
Add review information to results or code to justify why a bug fix is not required and hide from subsequent analyses. - Import Review Information from Existing Polyspace Access Projects
Transfer review information for findings from code that you reuse across projects. - Annotate Code and Hide Known or Acceptable Results (Polyspace Code Prover)
Look up the Polyspace code annotation syntax for justifying known issues.
- Define Custom Annotation Format (Polyspace Code Prover)
- Short Names of Code Prover Run-Time Checks (Polyspace Code Prover)
- Apply Existing Review Information to Identical Findings
Reuse justifications from one finding to justify similar findings at the same location in your code.