Hi Lenin,
You have to provide the specific situation or a reproduction code snippet to show why the Correctness Condition error is incorrect.
In Polyspace Code Prover, unlike Polyspace Bug Finder, you cannot disable specific checks. You can change the underlying assumptions so that certain aspects of a check are enabled or disabled. For instance, if you use the option -stubbed-pointers-are-unsafe, you enable the check for NULL on pointers from unknown sources.
In R2015b, the Correctness Condition check has been improved so that imprecise results are in orange instead of red. This change brings the Correctness Condition check in line with other run-time checks. See R2015b Release Notes . If you follow a policy of fixing all red checks and justifying orange checks as needed, this change can help you.
