"Jun-Kiat Lam" <[EMAIL PROTECTED]> wrote in message
news:16486@palm-dev-forum...
>
> Actually, it looks like the compiler is generating correct code; it's just
> that the debugger actually steps through several lines of instructions on
> that single line ....
I see what has happened. When the optimizer is turned on, then the debugger
visually skips statements that the program actually executes, and visually
executes statements that the program actually bypasses. Another "bug" we
observed is that when certain variables are assigned a value, other values
change as well; this must be because the optimizer assigns them the same
memory location (or register).
So the moral is, *always* turn off optimization before stepping visually
through code in the debugger.
Thanks for your analysis.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
