Bob Ebert,
Well thank God, someone got back to me. I was beginning to feel very
lonely. I have had this problem off and on for months now and I just
don't get it.
On Wed, 26 Apr 2000 21:06:15 +0200, you said:
>
> 1) are you sure it's the event pointer that's causing the problem?
No, but if it isn't something that /I/ am passing, what causes PalmOS
crash on me (and only me)?
> You
> should look carefully at the stack trace and the address that's being
> followed when the bus error occurs.
I have stared at the stack trace for hours. In the end though it is
just a bunch of numbers. I have no idea what the numbers are supposd to
be. Do you know of something I can compare them to in order to check
for validity?
>
> 2) It's possible for stack-based variables to be in invalid ranges. This
> happens when you overflow the stack!
I was getting stack overflow errors for a while due to creating local
variables without allocating memory like so...
Char displayStr[300];
Having realized the error of my ways, I went through and cleaned up
about 1 kB of variable space. Is there any way to determine the amount
of space on the stack? How much space should I allow for the PalmOS
routines to run smoothly?
I have noticed that the problems are 10times worse after an alarm is
displayed, but I don't know of any method for my program's alarm display
function to leave material on the the stack - presumably all variables
are de-allocated when the program's AlarmDisplayTriggeredAlarm routine
exits to the OS. Is there something I am missing?
derik
email: [EMAIL PROTECTED]
WWW: http://www.pobox.com/~derik
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
