Contact Technical Support About Issues with Running Polyspace

This topic describes what MathWorks^® Technical Support might need to troubleshoot issues encountered when running Polyspace^®. For similar information about Polyspace Access™, see Contact Technical Support About Polyspace Access Issues (Polyspace Access).

If you run into compilation errors or other issues after starting a Polyspace analysis or need help reviewing Polyspace results, check out troubleshooting tips in Troubleshooting in Polyspace Code Prover.

If you still cannot resolve the issue on your own, contact MathWorks Technical Support using this page. You need a MathWorks Account login and password. For faster turnaround with an issue in Polyspace, besides the required system information, provide appropriate code that reproduces the issue or the verification log file.

Provide System Information

When you enter a support request, provide the following system information:

Installed Polyspace products
License number
Operating system
Hardware configuration
Polyspace licenses available

To obtain your configuration information, do one of the following:

In the Polyspace user interface, select Help > About.

At the command line, navigate to your Polyspace installation folder, for instance C:\Program Files\Polyspace\R2024b (Windows^®) or /usr/local/Polyspace/R2024b (UNIX^®), and run the command that corresponds to your product and platform:

Product Command

Product	Command
Polyspace Bug Finder™ Polyspace Code Prover™	UNIX polyspace/bin/polyspace-bug-finder -ver Windows polyspace\bin\polyspace-bug-finder.exe -ver See also `-ver`.
Polyspace Bug Finder Server™ Polyspace Code Prover Server	UNIX polyspace/bin/polyspace-bug-finder-server -ver Windows polyspace\bin\polyspace-bug-finder-server.exe -ver See also `-ver`.

Polyspace Bug Finder™

Polyspace Code Prover™

UNIX
```
polyspace/bin/polyspace-bug-finder -ver
```

Windows

polyspace\bin\polyspace-bug-finder.exe -ver

Provide Information About the Issue

Depending on the issue, provide appropriate artifacts to help Technical Support understand and reproduce the issue.

Compilation Errors

If you face compilation issues with your project, see Troubleshoot Compilation Errors. If you are still having issues, contact technical support with the following information:

The analysis log.
The analysis log is a text file generated in your results folder and titled Polyspace_version_project_date_time.log. It contains the error message, the options used for the analysis and other relevant information.
The source files related to the compilation error or the complete results folder if possible.
If you cannot provide the source files:
- Try to provide a screenshot of the source code section that causes the compilation issue.
- Try to reproduce the issue with a different code. Provide that code to technical support.

Polyspace as You Code writes the contents of compilation error messages to a log file. The log is generated in your results folder and titled polyspace_err.log. Provide this log to technical support if you encounter a compilation issue with Polyspace as You Code.

Errors in Project Creation from Build Systems

If you face errors in creating a project from your build system, see Troubleshoot Project Creation.

If you are still having issues, contact technical support with debug information. To provide the debug information:

Run polyspace-configure at the command line with the option -easy-debug. For instance:
```
polyspace-configure options -easy-debug pathToFolder buildCommand
```
Here:
- options is the list of polyspace-configure options that you typically use.
- buildCommand is the build command that you use, for instance, make.
- pathToFolder is the folder where you want to store debug information, for instance, C:\Temp\BuildLogs. After a polyspace-configure run, the path provided contains a zipped file ending with pscfg-output.zip. The zipped file contains debug information only and does not contain source files traced in the build.
Make sure that you do not use the option -verbose or -silent after -easy-debug. These options reduce or modify the information logged and might make debugging difficult.
Send this zipped file ending with pscfg-output.zip to MathWorks Technical Support for further debugging.

You can also create the zipped file with debug information during every polyspace-configure run by creating an environment variable PS_CONFIGURE_OPTIONS and setting its value to:

-easy-debug pathToFolder

where pathToFolder is the folder where you want to store debug information.

Verification Result

If you are having trouble understanding a result or do not see an expected result, see:

Troubleshoot Results Review: This section describes common issues encountered when reviewing Polyspace results.
Complete List of Polyspace Code Prover Results: This section describes specifications of individual checkers, and might help explain a checker finding or why a checker does not show an expected finding.

If you are still having trouble understanding the result, contact technical support with the following information:

The analysis log.
The analysis log is a text file generated in your results folder and titled Polyspace_version_project_date_time.log. It contains the options used for the analysis and other relevant information.
The source files related to the result or the complete results folder if possible.
If you cannot provide the source files:
- Try to provide a screenshot of the relevant source code from the Source pane on the Polyspace user interface.
- Try to reproduce the problem with a different code. Provide that code to technical support.

Provide Polyspace Analysis Statistics File (Optional)

Depending on your issue, you might be asked to provide the .stats.zip file. The file is located in your results folder and contains statistics about your analysis, such as options used, time taken by the different phases of the analysis, and the memory consumed by the different processes that ran during the analysis. The file contains no identifying information about your code.