Identify Why Some Files or Functions are Missing in Polyspace Results

Issue

On the Results List pane, when you select File from the (Grouping) list, you do not see:

Some of your source files.
Some functions in your source files.

Possible Cause: Files Not Verified

If a source file or function does not contain a result such as a check or coding rule violation, the Results List pane does not display the file or function. If none of the operations in a source file or function contain a check, it indicates that Polyspace^® did not verify that source file or function.

To check if all files and functions were verified, see the Code covered by verification graph on the Dashboard pane. For more information, see Dashboard in Polyspace Desktop User Interface.

Solution

Polyspace does not verify a source file or function when one of the following situations occur.

Situation	Fix
The file or function does not contain an operation on which a check is required. For instance, a function contains calls to other functions only. If none of the called functions contains an error that lead to a Non-terminating call error in the calling function, the calling function does not contain a check.	No fix required.
All functions in the source file are not called, are called from unreachable code or are called following red checks. Polyspace does not verify the code that follows a red check and occurs in the same scope as the check. Therefore, it considers that the functions are not called and does not verify the file containing the functions.	If you choose to detect uncalled functions, the verification places a gray check on those functions. The functions and the source file containing the functions then appear on the Results List pane. For more information, see `Detect uncalled functions (-uncalled-function-checks)`.
Your code is intended for multitasking and you do not specify all your entry points. If all functions in a file are called from an entry point function that you did not specify, Polyspace does not verify the file.	See if you specified all entry points. For more information on how to specify entry points, see `Tasks (-entry-points)`. For a workflow on verifying multitasking code, see Configuring Polyspace Multitasking Analysis Manually.
If your source files do not contain a `main` function, Polyspace generates a `main` function. The generated `main` calls the functions that you specify using certain analysis options. If your analysis options are such that the generated `main` does not call all the functions in a source file, Polyspace does not verify the source file.	See if you have to change the `main` generation options associated with your verification. For more information on the options, see: `Initialization functions (-functions-called-before-main)` `Functions to call (-main-generator-calls)` `Class (-class-analyzer)` `Functions to call within the specified classes (-class-analyzer-calls)`.

Possible Cause: Filters Applied

If you rerun verification on a project module, filters from the last run are applied to the current run. Because of the persistent filters, some of the files can be hidden from display.

To check if some filters are applied, see the Results List pane header. The header shows the number of results filtered from the display. If you place your cursor on this number, you can see the applied filters.

For instance, in the image, you can see that the following filters have been applied:

The Checks & Rules filter to suppress code metrics and global variables.
The filter to suppress results found in a previous verification.
Filters on the Information and Check columns.

Solution

Clear the filters and see if your file or function reappears on the Results List pane. For more information, see Filter and Group Results in Polyspace Desktop User Interface.