Why am I having problems using the "-post-pre​processing​-command" option in PolySpace 5.1 (R2008a) and later?

For a PolySpace analysis task, when I use an old post-preprocessing-command (created before R2008a), or the post-preprocessing command example shown in the documentation, I get a compilation error. The error says:

The process tried to write to a nonexistent pipe.

Sometimes error message is propagated in C to intermediate language translation phase as: ERROR: ... ** C to intermediate language translation 14 (P_PT) exception Bind(Bind) raised. ...

Answer 1

[MathWorks Support Team]

This change has been incorporated into the documentation in Release 2009b (R2009b). For previous releases, read below for any additional information:

PolySpace 5.1 (R2008a) eliminated the Cygwin software dependency on Windows based machines. Since Cygwin software is no longer included in the PolySpace installation, all -post-preprocessing-command scripts created in earlier PolySpace releases must be updated to a pure Perl format if they mix shell and Perl commands.

To fix this compilation problem, you must use a pure Perl script and give the absolute path to the perl.exe file in the post preprocessing option. For example:

 -post-preprocessing-command [absolute_path_to]\perl.exe [absolute path script]\[sript.pl]

where [absolute_path_to] is %POLYSPACE_C%\Verifier\tools\perl\win32\bin in a standard PolySpace installation, and [absolute_path_script]\[script.pl] looks like the attached template.