I'm using the Full LabWindows/CVI 2010 SP1. To get the issue down to its simplest terms, I made a new user interface project from the template and inserted this code right before DisplayPanel was called:
char portString[1000];
portString[0] = '\0';
int length;
unsigned bytes[32];
int i;
for (i = 0; i < 10; i++)
{
length = sscanf (portString,
"%x %x %x %x %x %x %x %x %x %x %x %x %x %x %x %x"
"%x %x %x %x %x %x %x %x %x %x %x %x %x %x %x %x",
&bytes[0], &bytes[1], &bytes[2], &bytes[3],
&bytes[4], &bytes[5], &bytes[6], &bytes[7],
&bytes[8], &bytes[9], &bytes[10], &bytes[11],
&bytes[12], &bytes[13], &bytes[14], &bytes[15],
&bytes[16], &bytes[17], &bytes[18], &bytes[19],
&bytes[20], &bytes[21], &bytes[22], &bytes[23],
&bytes[24], &bytes[25], &bytes[26], &bytes[27],
&bytes[28], &bytes[29], &bytes[30], &bytes[31]);
}
When I run this in Extended debug mode for either Debug or Debug64, upon exiting the program, the Resource Tracking window says there are ten 510-byte memory buffers still allocated, and they all claim sscanf is the line that allocated the memory. The full application that this came from can do this a lot more than ten times. Should I be concerned about this? A memory leak can't be good.
Brian
