Add Review Information to Results
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.
Topics
- 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 Bug Finder)
Look up the Polyspace code annotation syntax for justifying known issues.
- Define Custom Annotation Format (Polyspace Bug Finder)
- Short Names of Bug Finder Defect Groups and Defect Checkers (Polyspace Bug Finder)
- Short Names of Code Complexity Metrics (Polyspace Bug Finder)
- Apply Existing Review Information to Identical Findings
Reuse justifications from one finding to justify similar findings at the same location in your code.