While working through some code examples in the book "21st Century C, 2nd Edition", using LabWindows/CVI 2017, I stumbled upon an interaction between the CVI debugger and globally declared pointers to pointers variables (**variable) that I don't understand. Below is a snippet of code that will replicate the observed behavior:
#include <stdio.h>
// Declare and initialize a global string array:
char **stringArray = (char* []) {"One", "Two", "Three"};
int main ()
{
for (int i=0; i<3; i++)
printf("Item %d: %s\n", i, stringArray[i]);
getchar(); // Allow the user to see the standard IO window
}
When the above code is built and run with the 32-bit debug configuration, with the Debugging Level set to "No run-time checking", the code outputs as expected:
Item 0: One
Item 1: Two
Item 2: Three
When run with the Debugging Level set to "Standard", the following error occurs:
NON-FATAL RUN-TIME ERROR: "StringArray.c", line 9, col 36, thread id 11656: Pointer is invalid.
So my questions are:
1.) Why does debugger throw this error on code that functions properly?
2.) Is there any way to selectively tell the debugger to ignore sections of code during runtime checking (e.g. with DEFINE's)?
