This is a compiler optimization and not a bug. You may want to check the
Palm-Dev-Forum archives for 'global register allocation' or 'register coloring'
to see more specifics on this particular issue and workarounds.
-- jkl
----- Original Message -----
From: "Paul Groschen" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, May 02, 2001 4:26 PM
Subject: Debugger Variable Corruption
> I have a fair amount of code running and debugged but today a strange
> problem occured.
> I am using CW version 7 using the emulator.
> I have a routine called during a menuEvent with the following test
> variables declared in my function: void SetModelNumber(UInt16 dataCount)
> {
> const void *bufP;
>
> UInt16 Value;
> UInt16 Palm0;
> UInt16 Palm1;
> UInt16 Book; ......
>
> The variables Palm0, Value and Book appear to be mapped to the same memory
> location, whenever 1 changes they all change.
>
> Any ideas on how to fix this? Is this a stack problem?
>
> Thanks
> Paul
>
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
