> > By making your stack a little smaller, your will overflow the
> > stack instead of
> > the interrupt routine. You can then find out what's filling up the stack.
>
> Thanks, I'll give this a try.
Please read my more recent posting on this. Attempting to establish your own
stack with a 'pref' resource will not work during boot/reset time. At that
time, you're using the OS's stack, not your own.
> > By the way, the emulator usually warns when the application is
> > getting close to
> > overflowing the stack (within 50 bytes of the end). I wonder why
> > you're not
> > seeing that warning.
>
> FYI, I do have all the debugging options checked "on" in POSER, including
> warning about stack overflows. I have never received a stack overflow in
> the course of running my app. I now have deduced it only happens when I
> reset POSER after having brought up the main screen of my application. I'm
> sure it's some kind of bug in handling frmOpen, frmUpdate etc, that happens
> when the app first starts.
Actually, as implied in my more recent posting in this thread, I now realize why
you're not getting the "stack is almost overflowed" warning message. I had
missed the fact that you're getting this at Reset time. At that time, the OS's
stack is in use, not yours. While implementing stack overflow checking, I found
that the OS got awfully close to overflowing the stack during Reset, and even
overflows it in Palm OS 3.3. Therefore, I inhibit the "almost overflowed" error
message when the OS stack is in use.
-- Keith Rollin
-- Palm OS Emulator engineer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
