"Daniel Zucker" <[EMAIL PROTECTED]> wrote in message
news:12419@palm-dev-forum...
> When I clicked on a local stack
> variable whose value was 0 and clicked "view memory", instead of showing
me
> the memory address of the variable, it jumped me to the 0x0000 memory
> location.
I suspect the compiler used a register for that variable.
> In general I find that I can't really
> trust the values that CodeWarrier is showing me for variables.
In general, you should only trust the top stack frame (last in list IIRC).
Variables stored in registers will often show the wrong values in other
stack frames because the register was reused. The debugger could
(theoretically) look on the stack where the register was saved, but it
doesn't do this. Turning off compiler optimizations generally helps the
debugger. It should solve both of these problems.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
