"Steve Mann" <[EMAIL PROTECTED]> wrote in message
news:62540@palm-dev-forum...
>
> >The other solution would be to disable optimizations and recompile
your
> >application while you're debugging. In CodeWarrior, you do this by
> >going to the Global Optimizations panel and moving the slider to
level
> >0.
>
> I always develop with all optimizations turned off and I still have
> that problem. The variable contents are displayed as "Register is
> unavailable". I was under the impression that CodeWarrior always
> allocates some variables to registers, even with optimizations turned
> off, and it can't guarantee the values in those registers.
With optimizations at 0, all local variables will be represented as
offsets from the frame pointer, register A6.
The previous A6 is stored on the stack, just before the return address
used to go back to the caller. If you've written bad code that
overwrites this value, the debugger could show this "register is
unavailable" message when you inspect previous stack frames.
I don't know of other situations where that would pop-up at opt 0, but
we'd be glad to see examples. Its more likely that its a debugger bug
than a code generation bug.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
