Main Content

Product mode

Choice between Polyspace Bug Finder and Polyspace Code Prover

Since R2021b

Model Configuration Pane: Polyspace

Description

The Product mode parameter determines whether to perform a Polyspace® Bug Finder™ analysis or a Polyspace Code Prover™. These different analyses have different goals. Bug Finder quickly analyzes your code to detect coding rule violations and various defects. Code Prover checks every operation in your code for a set of possible run-time errors and tries to prove the absence of the error for all execution paths. See Differences Between Polyspace Bug Finder and Polyspace Code Prover.

Note

For each operation in your code, Code Prover considers all execution paths leading to the operation that do not have a previous error. If an execution path contains an error prior to the operation, Code Prover does not consider it. See Code Prover Analysis Following Red and Orange Checks.

You can find this parameter in the Polyspace pane of the Configuration Parameters dialog box, in the Advanced parameters section.

Settings

Code Prover (default) | Bug Finder
Bug Finder

Polyspace Bug Finder analysis on the generated code.

Code Prover

Polyspace Code Prover analysis on the generated code.

Recommended Settings

ApplicationSetting
DebuggingNo Impact
TraceabilityNo Impact
EfficiencyNo Impact
Safety precautionNo Impact

Programmatic Use

Parameter: VerificationMode for use with pslinkoptions
Parameter: PSVerificationMode for use with set_param()
Values: 'BugFinder' | 'CodeProver'
Default: 'CodeProver'
Example: opt = pslinkoptions(modelname); opt.VerificationModel = 'BugFinder';

Version History

Introduced in R2021b

See Also

|

Topics