Polyspace (R2016b) Win64: I get exception path(path) when I try to run a analysis from commandline

Hi,

I created a options file with the Polyspace-configure command. When I try to run the analysis with polyspace-bug-finder-nodesktop and this file I just get the following exception:

Unexpected exception raised during ps_pckg.so call:
exception Path(Path) raised.

What is my Problem and how can I avoid it?

Thanks

[Manan Mishra]

Can you share the exact commands you are using to create the options file and to run analysis?

[Volker Trucksees]

Shure. To create the optionsfile I used (from Visual Studio Command Prompt):

polyspace-configure -prog D:\Daten\Volker\EigeneDokumente\Hochschule\Stuttgart\Masterarbeit\Volker\Polyspace_Workspace\CWE114\CWE114.psprj -output-options-file \CWE114_Options.txt cl /I..\..\testcasesupport /W3 /MT /GS /RTC1 /bigobj /EHsc /nologo /c main.cpp CWE*.cpp CWE*.c ..\..\testcasesupport\io.c ..\..\testcasesupport\std_thread.c

And the exception appears when I try to run: polyspace-bug-finder-nodesktop -options-file CWE114_Options.txt -results-dir D:\Daten\Volker\EigeneDokumente\Hochschule\Stuttgart\Masterarbeit\Volker\Polyspace_Workspace\CWE114

I also tryed with "/" instead of "\"

[ADITI AJAYKUMAR SHENOY]

Hey,

Can you please let me know the exact command and the options file?

I have windows header errors. Its says can't find include files windows.h winsock2.h.

Regards,

Aditi

Answer 1

[Manan Mishra]

In Polyspace releases prior to R2017b, the "-prog" flag in "polyspace-configure" command expects only the name of your Polyspace project and not the full path.

The following documentation gives the syntax and description for the same:

Specify name of project

In cases when "-prog" is not a real name but a path, the verification fails with the error you are receiving.

You can try giving just the project name with "-prog" and see if it works. For example, "-prog CWE114".

This issue has been fixed in Polyspace R2017b.