Main Content

Verification time limit (-timeout)

Specify a time limit on your analysis

Description

Specify a time limit on a Polyspace® Bug Finder™ or Polyspace Code Prover™ analysis in hours. If the analysis does not complete within that limit, it stops.

Set Option

User interface (desktop products only): In your project configuration, the option is available on the Precision node.

User interface (Polyspace Platform, desktop products only): In your project configuration, the option is on the Static Analysis tab on the Computing Settings node.

Command line and options file: Use the option -timeout. See Command-Line Information.

Why Use This Option

Use this option to impose a time limit on the analysis.

For instance, if an internal step in a Code Prover analysis lasts for more than 24 hours, the analysis stops. You can use this option to reduce the time limit even further. Note that you can have analysis results despite the analysis timing out. For instance, if a step in Software Safety Analysis level 1 (Code Prover) times out, you still get the results from level 0. See Verification level (-to).

The option is useful only in very specific cases. Suppose your code has certain constructs that might slow down the analysis. To check this, you can impose a time limit on the analysis so that the analysis stops if it takes too long.

Typically, Technical Support asks you to use this option as needed.

Settings

Enter the time in hours. For fractions of an hour, specify decimal form.

Command-Line Information

Parameter: -timeout
Value: time
Example (Code Prover): polyspace-code-prover -sources file_name -timeout 5.75
Example (Code Prover Server): polyspace-code-prover-server -sources file_name -timeout 5.75
Example (Bug Finder): polyspace-bug-finder -sources file_name -timeout 5.75
Example (Bug Finder Server): polyspace-bug-finder-server -sources file_name -timeout 5.75