Why is Polyspace showing under the Code Metrics that the code metrics Maximum and Minimum Stack Usage are "Not computed"?

When computing and uploading the results of a Polyspace verification for a given Polyspace project and then uploading them to Polyspace Access, then the metrics Maximum and Minimum Stack Usage are shown as "Not computed" under the section "Code Metrics", namely,

Maximum Stack Usage Not computed
Minimum Stack Usage Not computed

However, the sentence "Not computed" is hyperlinked and clicking on it leads to another page where the Maximum and Minimum Stack Usage code metrics are displayed as expected for the corresponding functions.

Why is Polyspace showing under the Code Metrics that the code metrics Maximum and Minimum Stack Usage are "Not computed"?

Answer 1

[MathWorks Support Team]

Please check that all files are properly compiled and that there are no errors in the compilation.

Clicking on the hyperlink "Not computed" should show the functions for which the corresponding code metrics are computed and the ones forwhich have the corresponding code metrics are not computed.

If there are errors in the compilation, then this can cause that the code metrics are not computed for some functions in the corresponding source files. To have the code metrics shown in Polyspace Access one needs to have all the functions properly compiled in Polyspace and then upload the results on Polyspace Access.

I guess it is root cause: functions in ManiLab.c may have code metrics whereas only code metrics are populated in Polyspace Access after upload.

[Anirban]

Other reasons why stack usage might not be computed at all are documented in Determination of Program Stack Usage.