Compilation Errors when running Static analysis for a C Application

I am using the R2025b release of the Polyspace bug finder to perform Static Analysis on our C application. But due to compilation errors we observe that a lot of files are 'partially analyzed' as specified in the generated report. We have included paths to all the libaries and toolchain we have used and set the compiler to armcc as the appication is built for arm based linux system. But the compilation error still persist. Please provide a solution.

We are running the Polyspace Bugfinder release: R2025b on a 64 bit Windows Operating System.

Answer 1

[Sanathan]

Hello Reghu

Polyspace Bug Finder marks files as "partially analyzed" when compilation errors prevent full static analysis, even after specifying libraries, toolchains, and the armcc compiler.

As you mentioned you have provided paths to armcc, recheck the standard library headers, since Polyspace requires them explicitly to avoid fallback to its own headers. Without these, errors like missing headers or undefined identifiers persist; verify paths match your ARM toolchain installation.

Refer to this about header issues - https://www.mathworks.com/help/bugfinder/ug/standard-library-function-stubbing-errors.html

If that doesn't work, Refer to the following documentation links. You may get an idea to troubleshoot the root issue.

1. https://www.mathworks.com/help/bugfinder/ref/armv5compilercompilerarmcc.html
2. https://www.mathworks.com/help/polyspace_access/ug/troubleshoot-polyspace-as-you-code.html
3. https://www.mathworks.com/help/bugfinder/ug/undeclared-identifier.html

If you are still unable to find a solution, please contact Technical Support.