Non-initialized variable in __polyspace_main.c

If I enable the option "Ignore default initialization of global variables", I get orange alarms on the Macro PST_TRUE() in the __polyspace_main.c, which is the volatile variable pst_random_int. I want the Code Prover to detect not-initialized variables in my code, but not to use non-initialized in the automatically generated main. My expectation is that polyspace handles the self-generated global variables for itself and only report errors on code like this:

uint8 myGlobalVariable;

void main()
{
   uint8 a;
   a = myGlobalVariable;
}

What have I to adjust to get the behavior described above? And why does I get alarms on the generated Polyspace files at all?

Answer 1

[Lucas Lebert]

Hi, Patricia! Unfortunately, there's no workaround for this NIV orange check prior to R2017a. Starting in R2017a, the global variable in the generated main should no longer be raised. If the issue still persists in more recent releases, feel free to contact the MathWorks technical support. Have a great day, Lucas