Identify Why Some Files or Functions are Missing in Polyspace Results

Issue

This topic describes some reasons why you do not see results from certain files in your Polyspace^® Code Prover™ analysis results. For instance, when you enter the file name in the Show only search box on the Results List pane, all results disappear from the list. Instead you see the following message:

No results found for currently applied filters or selected project has no results

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 Analyzed By Verification graph on the Dashboard pane. For more information, see Dashboard in Polyspace Platform 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

When you open a result set in the Polyspace Platform user interface, filters applied to the previous open results continue to be active. 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.

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

The Run-time Checks filter to show only Code Prover run-time checks.
The Done filter to show only results that are marked with one of the statuses that indicate the result has been reviewed. For more information on the statuses, see Address Polyspace Results Through Bug Fixes or Justifications.

Solution

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