Polyspace bug finder creates wrong options file via cmd call but via GUI it is valid

Hey guys,

I would like to run my polyspace analysis via a cmd call using a make file (created with S32DS) from our project. For this I followed the instructions from the manual on the following website https://de.mathworks.com/help/bugfinder/ug/run-analysis-from-the-command-line.html (Create Options File from Build System).

The call looks like:

polyspace-configure -easy-debug <Pfad> -output-options-file compile_opts C:\\NXP\S32DS.3.4\eclipse\eclipsec.exe -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data <ProjectPath> -cleanBuild <ModulePath>

Unfortunately, the options file cannot be executed with polyspace-bug-finder, because the option -dialect is created here, which is then displayed as error "unknown". Furthermore, an incorrect compiler is detected. To verify this error I built the project with the same build command but this time via the GUI and the options file created is correct.

Now my question is why there is this difference at all and how do I get the same result from the GUI with a cmd execution?

Answer 1

[Anirban]

The option -dialect is an old option that has been renamed to -compiler. Can you see if changing the option -dialect to -compiler helps you work around the issue? The old option name should not have been generated and might be a specific bug you ran into.

You also mention that the compiler name is incorrect. What is the correct compiler name and what is the incorrect name generated?

[Andreas]

Thanks for the answer.

Indeed changing the option -dialect to -compiler solves the problem but I want to create the options file fully automatically without changing anything afterwards.

The paradox is, when I create a new project via the gui using the same build command (via makefile), the options file here contains much more options, which are correct. I´m expecting -compiler gnu6.x.

How do I get exactly the same options file with the cmd call as with manually via the GUI?

[Anirban]

The same underlying command (polyspace-configure) is used whether you run from the command-line or GUI. So the paradox should not happen in principle.

I think, more detailed reproduction steps are needed to understand what is going on. Please contact MathWorks Technical Support to help you diagnose the issue. For more information on what Technical Support would need, see Contact Technical Support.

I can only think of one thing here: when you say 'create a new project via the gui', are you doing the steps detailed here? Are you entering the option -output-options-file in the field Add advanced configure options and is that how you are getting an options file? Typically in a GUI workflow, the options are generated in the project itself, so the option -output-options-file is not needed. Anyway, if this is what you are doing in the GUI, in the Command Output window, you should be able to see the command being run. Is that somehow different from what you are running at the command line? That might give a possible clue as to what is happening.

Another remote possibility is that you have several versions of Polyspace installed, and because of an environment variable setting, you happen to be using an older version of Polyspace at the command line.

[Andreas]

Indeed, I accidentely used different versions of Polyspace due to environment variable settings.

Thank you!