Main Content

Review Bug Finder Results

R2026b
Interpret Polyspace® Bug Finder™ defects and coding rule violations, trace results to root cause, and add review information

After analysis, review results in the Polyspace Access™ user interface. You can do one of the following:

  • Start reviewing results immediately in your web browser.

  • Export Results from Polyspace Access.

  • 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.

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

expand all

polyspace-access -set-project-information(System Command) Set project-specific information
polyspace-access -unset-project-information(System Command) Remove project-specific information
polyspace-access -review(System Command) Edit review information of results for project
polyspace-access -import-reviews(System Command) Import review information from source project to target project
polyspace-access -add-label(System Command) Add label to project run
polyspace-access -remove-label(System Command) Remove label from project run
polyspace-access -set-unassigned-findings(System Command) Assign owners to unassigned results

Topics

Getting Started

Understanding Bug Finder Results

Polyspace Access Dashboard View

Add Review Information to Results

Related Information