Troubleshooting in Polyspace Code Prover
If you encounter unexpected issues when setting up or running a Polyspace Code Prover analysis, check this troubleshooting guide for workarounds.
Unexpected issues while running Polyspace analysis include:
Compilation errors
License errors, database corruption, or temporary folder restrictions
Project creation errors
Server not found or other analysis errors on remote clusters
Memory usage or analysis time errors
Errors while running Polyspace analysis of generated code or custom code included in Simulink® models.
Unexpected issues while reviewing results include:
Result interpretation such as unclear orange checks.
Report generation such as insufficient memory errors or unsatisfactory reports.
If you are experiencing unexpected errors while installing Polyspace Code Prover, see Install Polyspace for detailed installation instructions.
Categories
- Troubleshoot Running Polyspace Analysis
Compilation errors, errors connecting to server, errors creating Polyspace project, and so on
- Troubleshoot Results Review
Unchecked code, report generation errors, unclear orange checks, and so on