Hi Mohammed,
I understand that you are receiving an error when you try to execute a C project on Polyspace 2012b.
This problem can happen for large verifications and when the queue manager machine is also the cpu (server), i.e. the queue manager and the cpu are not separate machines.
It is the unzip of the archive process (server side then) that takes too much time (more than one minute).
The first workaround is to "separate" the queue manager and the CPU, so they are two distinct machines.
Another non-trivial solution if it's not possible, is to have two deamons (polyspaced) on the same machine, one for the queue manager and one for the cpu. To do that:
- create a new Polyspace_RLDatas folder for the cpu (let's call it Polyspace_RLDatas_cpu for example)
- in this folder, create a polyspace.conf for the cpu, based on the one for the queue manager
- edit this polyspace.conf and change the port number (so the queue manager and the cpu don't communicate on the same port)
- for the same reasn, change the datadir so it points to Polyspace_RLDatas_cpu
- remove the line cpu=...
Modify the polyspace.conf of the queue manager: edit the line cpu=... to add the :<port> at the end of the line (<port> is the port used by the cpu)
Now start the new "cpu daemon".
- On Windows: in a Dos shell, type
set POLYSPACE_CONFIGURATION_FILE=<path_to_the_cpu_polyspace.conf>
<path_to>\polyspaced.exe
You can make a .bat script to perform these two actions.
- On Linux:
export POLYSPACE_CONFIGURATION_FILE=<path_to_the_cpu_polyspace.conf>
<PathTo>/PolyspaceForCandCPP_R2013a/polyspace/bin/polyspaced
Hope this helps
