Here is how to get debug log files with polyspace-configure issues, before contacting the MathWorks support:
Before R2020a
Relaunch polyspace-configure with some extra options. More precisely, here is the procedure:
- Before relaunching polyspace-configure, be sure that the build command will compile C and/or C++ files again by doing a clean build (i.e. the object files have been deleted). For example, if you are using make, please do a 'make clean' before executing the command below.
- Then execute: polyspace-configure -build-trace build_trace.log -keep-all-files -debug <your build command> > out.log 2>&1
then send the two log files build_trace.log and out.log generated this way. The two files don't contain IP information.
If polyspace-configure generated a configuration file, send also the Polyspace log file that was utilized with it.
Since R2020a
There is a new option that can be used with polyspace-configure: -easy-debug.
Before using it when calling polyspace-configure, first remove old build artifacts to do a clean rebuild of your code (to ensure that all the source files are compiled during the build), and then launch:
polyspace-configure ... -no-compiler-cache -easy-debug <folder> <your build command>
The folder <folder> will contain a zip file that you should send to the support. The files in the zip don't contain IP information.
If polyspace-configure generated a configuration file, send also the Polyspace log file that was utilized with it.
Please also ask:
- the options file or project file created by polyspace-configure (if it exists)
- the Polyspace analysis log to see the exact error message
