What to do when facing "scaling behavior" with Polyspace Code Prover?
조회 수: 37 (최근 30일)
이전 댓글 표시
MathWorks Support Team
2016년 8월 5일
편집: MathWorks Support Team
2023년 8월 28일
When using the Polyspace Code Prover, I encountered the following different scenarios:
i) An "out of memory" error, for example:
**** Software Safety Analysis Level 0 - 61 (P_ILOI)
**** Software Safety Analysis Level 0 - 61 (P_ILOI) took 2.13real, 1.92u + 0.03s
**** Software Safety Analysis Level 0 - 62 (P_ENVT)
Fatal error: out of memory.
ii) A 24-hour timeout (timeout after 86400 seconds), for example:
***** Software Safety Analysis Level 0 - 32.2 (P_I1)
Warning: The analysis has been stopped by timeout (after 86400 seconds).
Maximum Memory Usage: 1720 MB
or:
4.5.2.1.1 (Loading) took 0.27real, 0.21u + 0.05s (0.1gc)
[64928 -> 192289]
Warning: The C2IL translation has been stopped by timeout (after 86400 seconds).
iii) An analysis showing no progress.
These seem to be symptoms of a "scaling behavior" with the Polyspace Code Prover. What are some solutions to these behaviors?
채택된 답변
MathWorks Support Team
2023년 7월 27일
편집: MathWorks Support Team
2023년 8월 28일
Please find the attached PDF file for a guide on scaling behaviors for Polyspace Code Prover, which includes explanations on how to identify scaling behaviors, and the solutions against these different scenarios.
댓글 수: 0
추가 답변 (0개)
참고 항목
카테고리
Help Center 및 File Exchange에서 Code Prover Analysis in Simulink에 대해 자세히 알아보기
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!