Repetitive unreal orange checks

Hi,

Am working currently on Run time errors checks using Polyspace Code Prover and Bug finder and after running step is over, i got a lot of orange checks, mostly Non initialized variables and illegally dereferenced pointers which in fact are justified after tracing them. I wonder if there is a way to avoid that by manipulating the polyspace configuration or editing the stubbed functions file?

Thanks

Answer 1

[Alexandre De Barros]

Hello,

When dealing with orange checks, a good rule of thumb is to find the source of these checks so you can "work on it".

The GUI actually gives you this information first in the dashboard (see the graph 'Top 5 orange sources') and in the dedicated window named 'Orange Sources'.

Tip: when reviewing an orange check, in the 'Check details' or 'Result details' window, the "orange question mark" icon, when it is enabled, will open this 'Orange Sources' window and highlight the source for this orange check.

If you launch Polyspace in command line, the 'orange source' information is also available in the log file (look for 'Classification of orange check sources').

Once you know the source(s), the DRS and the stubbing are the main ways to reduce the number of orange checks.

For more information on how to deal with orange checks, please refer to the documentation, for example here.

Best regards,

Alexandre