Compilation Errors when running Static analysis for a C Application

22 次查看（过去 30 天）
Reghu
Reghu 2025-11-20，9:53
回答： Sanathan about 13 hours 前
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.

请先登录，再回答此问题。

回答（1 个）

Sanathan
Sanathan about 13 hours 前
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.

类别

在 Help Center 和 File Exchange 中查找有关 Run Settings 的更多信息

标签

产品


版本

R2025b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by