Article ID: 128897
Article Last Modified on 7/5/2005
APPLIES TO
- Microsoft Visual C++ 2.0 Professional Edition
- Microsoft Visual C++ 2.1
This article was previously published under Q128897
SYMPTOMS
If you access a structure member when using an unsigned char index in a For loop, a general protection (GP) fault occurs.
CAUSE
When the compiler is optimizing for speed, only the low byte of the register where the index is stored is zeroed. Later on, the full extended register is used in calculating the offset of the structure member. Because the rest of the register is never zeroed, the offset used is invalid.
RESOLUTION
Use either one of the following workarounds:
- Change the type of the For loop index to any type other than unsigned char. -or-
- Do not use speed optimizations.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Microsoft Visual C++, 32-bit Edition, version 4.0.
MORE INFORMATION
The sample code below can be used to demonstrate the problem.
Due to the complexity of the optimization algorithm, some structures may work while others fail. However until this bug is fixed, it should be considered unsafe to use unsigned char indexing in a For loop with speed optimization.
Sample Code to Reproduce Problem
/* Compile options needed: any speed optimizations
*/
struct TEST
{
char filler[37];
int x;
} xyz[2];
void main()
{
unsigned char i = 1;
for(i=0; i<2; i++)
{
xyz[i].x = -1;
}
}
Additional query words: 2.00 2.10 VCx86 GPF
Keywords: kbbug kbfix kbcompiler KB128897
