Results Review Process

Review run-time errors systematically, specify review level, review checks using methodology, view call sequence and variable access graph, comment checks

Examples and How To

Review Results

Review Red Checks

Investigate why an operation in your code is certain to cause a run-time error.

Review Gray Checks

Investigate why a block of code is unreachable.

Review Orange Checks

Investigate why an operation in your code can potentially cause a run-time error.

Review Global Variable Usage

Investigate why a global variable is unprotected or unused.

Add Review Comments

Add Review Comments to Results

If you do not want to fix your code right away, leave comments in the verification results to avoid another review.

Add Review Comments to Code

If you do not want to fix your code, leave comments directly in your code to justify why a fix is not required.


Verification Following Red and Orange Checks

Learn how an operation containing a run-time error affects verification of subsequent code.

Polyspace Check Colors

Learn what the colors in your verification results mean.

What Is an Orange Check?

Learn why the verification cannot prove the presence or absence of an error for certain operations.

Sources of Orange Checks

Orange checks can be separated into two categories:

Result Views in Polyspace User Interface

Understand how you can use the various windows in the Polyspace® user interface to diagnose a result.

Why Review Dead Code Checks

Learn why you must review grays checks representing unreachable code.

Was this topic helpful?