> Ah...you have an interesting edge case here.
Oooooo... edge case!
> * Make the stack size a little smaller and run your application
> again. See:
>
> <http://oasis.palm.com/dev/kb/faq/1214.cfm>
>
> 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.
> * Generate a stack crawl by hand. This *can* be done, but if you
> don't know how
> to do it, then it would probably take me too long to explain it here.
I don't know about stack crawls, so I'll try to survive without it.
> 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.
Thanks everyone for all the suggestions.
Mitch
> For information on using the Palm Developer Forums, or to
> unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
