What to do when facing "scaling behavior" with Polyspace Code Prover?
38 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
MathWorks Support Team
le 5 Août 2016
Modifié(e) : MathWorks Support Team
le 28 Août 2023
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?
Réponse acceptée
MathWorks Support Team
le 27 Juil 2023
Modifié(e) : MathWorks Support Team
le 28 Août 2023
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 commentaires
Plus de réponses (0)
Voir également
Catégories
En savoir plus sur Code Prover Analysis in Simulink dans Help Center et File Exchange
Produits
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!