(I'm using CW R6, Pose 3.0a6, and SDK 3.5 update 1 on a PowerBook G3.)
Hey Jun-Kiat, thanks for the advice! I threw out the CW Debugging Cache and
CW Autosave stuff. I also made sure that compiler optimizations were
off (which they were). Things are a little better now. I'm also
stepping through my code more slowly. A few times I've had
CodeWarrior exit with no notification when I've clicked to change an
existing break point. Another time I chose "Clear All Breakpoints"
from the Debug menu and CW exited in the same way. I'm not sure
what's causing that. When something goes wrong I'm still having to
reboot my machine. But it looks like there is now a one to one
correspondence between the code that's being executed and the code
that the debugger says is being executed. I'll see if I can figure
out any more details of when weird things are happening.
Eric
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
