Can we stop run time checks in code prover for static analysis ?

when I am runnig code prover for my code , I see there are some run time checks also performed but can we stop that somehow from configuration and only see my MISRA rule violations ?

[Torsten]

If you want official MathWorks employees to answer your question, contact support:

https://uk.mathworks.com/support/contact_us.html

Here is the answer from AI:

No, you cannot selectively disable run-time checks from the engine configuration in Polyspace Code Prover. Because Code Prover uses formal mathematical methods to guarantee the safety-critical absence of runtime errors, MathWorks intentionally prevents you from completely turning off these core checks. Furthermore, modern versions of Polyspace have deprecated and removed MISRA coding rule checks from Code Prover entirely. [1, 2]

To get the clean view you are looking for, you must change your workflow using one of the two strategies below:

Strategy 1: Use Polyspace Bug Finder (Recommended if you have a licence for it)

MathWorks designed Polyspace Bug Finder specifically to check for coding standards like MISRA and lightweight defects. If you want to check your code strictly for MISRA rule violations without running exhausting mathematical proofs for run-time errors, you should use Bug Finder instead of Code Prover. [1, 2, 3, 4]

• Open your project configuration.
• Ensure you select the Bug Finder analysis type rather than Code Prover.
• In your configuration settings, go to Coding Rules & Code Metrics.
• Enable your desired MISRA standard (e.g., MISRA C:2012 or MISRA C:2023).
• Go to Bug Finder Analysis > Disable Defect Checkers (-checkers none) so that it only outputs MISRA violations. [1, 2, 3, 4, 5, 6]

Strategy 2: Filter the Results UI (If you must stay in Code Prover)

If your legacy setup mandates that you must run a joint analysis or review an existing Code Prover output, you cannot prevent the tool from calculating run-time checks, but you can hide them instantly via the Polyspace User Interface or Access Dashboard: [1]

• Run your analysis.
• In the Results or Filter pane (typically located on the left or top-right of your UI), look for the Family or Group classification.
• Uncheck Run-Time Errors (which hides Red, Orange, Gray, and Green checks).
• Check Coding Rules (this isolates only the MISRA violations in your active window). [1, 2]

Comparison of Workflows

Capability Polyspace Bug Finder Polyspace Code Prover

Primary Focus MISRA compliance, quick bug Exhaustive mathematical proof

finding, and code metrics. of run-time safety.

Disable Run-Time Yes (set -checkers none). No (integral to the proof engine).

Checks?

Analysis Speed Fast (minutes). Slow (deep mathematical context needed).