Before contacting MathWorks Support, please collect the debug log files related to polyspace-configure by following the procedure corresponding to your Polyspace version:
For Versions Prior to R2020a
You need to relaunch polyspace-configure with additional debug options.
Procedure
- Perform a clean buildBefore running polyspace-configure, make sure your project will recompile all C and/or C++ source files. This requires removing existing build artifacts (object files).For example, if you are using make, run
make clean
- Run polyspace-configure with debug optionsExecute the following command, replacing <your build command> with your actual build command:
polyspace-configure -build-trace build_trace.log -keep-all-files -debug <your build command> > out.log 2>&1
- Send the generated log filesPlease send the following files to MathWorks Support:
These files do not contain any intellectual property (IP).
- Optional: configuration file generatedIf polyspace-configure generated a configuration file, also include the Polyspace analysis log file that was used with this configuration.
For Versions R2020a and Later
A dedicated option is available to simplify debug data collection: -easy-debug.
Procedure
- Perform a clean buildAs with earlier versions, first remove any existing build artifacts to ensure that all source files are compiled again.
- Run polyspace-configure with -easy-debugUse the following command:
polyspace-configure ... -no-compiler-cache -easy-debug <folder> <your build command>
Replace <folder> with a directory name of your choice.
- Send the generated ZIP fileThe specified <folder> will contain a ZIP archive. Please send this ZIP file to MathWorks Support.The files included in the ZIP archive do not contain any IP information.
- Optional: configuration file generatedIf polyspace-configure generated a configuration file, also include the Polyspace analysis log file that was used with it.
Additional Files to Provide
In all cases, please also send:
- The options file or project file generated by polyspace-configure (if it exists)
- If polyspace-configure was able to generate a configuration file for the analysis, it is important to provide the corresponding Polyspace analysis log file as well. The analysis log contains the error messages required by Support to investigate the issue efficiently and identify the root cause more quickly.