| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → PolySpace |
| Contents | Index |
| Learn more about PolySpace |
| On this page… |
|---|
The PolySpace Viewer window looks like this.

The appearance of the Viewer toolbar depends on the Viewer mode. Because the Viewer is in expert mode, the expert mode toolbar is displayed.

In both expert mode and assistant mode, the Viewer window has six sections below the toolbar. Each section provides a different view of the results. The following table describes these views.
| This view... | Displays... |
|---|---|
| Procedural entities view (lower left) | List of the diagnostics (checks) for each file and function in the project |
| Source code view (lower right) | Source code for a selected check in the procedural entities view |
| Coding review progress view (upper left) | Statistics about the review progress for checks with the same type and category as the selected check |
| Selected check view (upper right) | Details about the selected check |
| Variables view | Information about the global variables declared in the source code |
| Call tree view | Tree structure of function calls |
You can resize or hide any of these sections. You learn more about the Viewer window later in this tutorial.
The procedural entities view, in the lower-left part of the Viewer window, displays a table with information about the diagnostics for each file in the project. The procedural entities view is also called the RTE (Run-Time Error) view. When you first open the results file from the verification of example.adb, the procedural entities view looks like this.

The package RUNTIME_ERROR is red because its contains at least one definite run-time error. PolySpace software assigns each package the color of the most severe error found in that package. Note that the other entities displayed for the example project are simply black. This indicates that they contain specifications that were used for the analysis. The first column of the Procedural entities view names the procedural entity (the package or function). The following table describes some of the other columns in the procedural entities view.
| Column Heading | Indicates |
|---|---|
| Number of red checks (operations where an error always occurs) |
| Number of gray checks (unreachable code) |
| Number of orange checks (warnings for operations where an error might occur) |
| Number of green checks (operations where an error never occurs) |
| Selectivity of the verification (percentage of checks that
are not orange) This is an indication of the level of proof. |
Tip
If you see three dots in place of a heading,
|
Note You can select which columns appear in the procedural entities view by editing the preferences. To learn how to add a Reviewed column, see Making the Reviewed Column Visible. |
What you select in the procedural entities view determines what is displayed in the other views. In the following examples, you learn how to use the views and how they interact.
![]() | Opening the Viewer and the Verification Results | Reviewing Results in Expert Mode | ![]() |
| © 1984-2010- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |