Hi,
I am guessing when you mention failure of the polyspace function, you mean a failure because of compilation errors in the source code or some such thing. In those cases, a better approach would be to poll the return value of the polyspaceCodeProver function, like so:
status = polyspaceCodeProver('-sources',sourceFileName,...
'-I',includeFileName, ...
'-results-dir',resFolder2,...
'-misra3','mandatory',...
'-do-not-generate-results-for','all-headers',...
'-main-generator');
If the verification fails, the function returns 1 to the status variable, otherwise 0.
A similar approach is given for the polyspace.Project object in Troubleshoot Polyspace Analysis from MATLAB. This object provides a cleaner way to run Polyspace from MATLAB. So, you can also use this object instead of the polyspaceCodeProver function.
