Wondering if anyone else has experienced this...
We have a testing mode for our application that lets testers "fast-forward" time to
just before the next alarm is supposed to fire. When they activate this feature, the
code just gets the time for the next alarm and then uses TimSetSeconds to set the
device clock to 1 minute before that alarm is to fire. This works fine.
However, somewhere around the 15th or 16th TimSetSeconds, the OS crashes with a fatal
alert Chunk Overlocked.
I do not register for the Time changed notification. (Should I?).
I cannot duplicate this problem by just changing the system clock via the preferences.
But I can make it happen from there if I've also changed the time from my
application....
We also synchronize the device's time to the time on a server every time the user
synchronizes their data. Again, if we do about 15 or 16 TimSetSeconds in this
scenario, we crash with a chunk overlocked fatal alert. This TimSetSeconds happens
during AppStart.
Since I cannot duplicate this problem without our application having run at least
once, I wonder if I'm missing something...
Thanks,
Kevin
Kevin O'Keefe
Senior Software Engineer
invivodata, inc. �
the science of patient experience�
5615 Scotts Valley Drive
Scotts Valley, CA 95066
Tel: (831) 438-9527
Fax: (831) 440-1770
email: [EMAIL PROTECTED]
<http://www.invivodata.com>
------------------------------------------
The information in this transmittal and any attachments are confidential and intended
only for the recipient(s) listed above. You are hereby notified that any unauthorized
distribution or copying of this transmittal or its attachments is prohibited. If you
have received this transmittal in error, please notify invivodata immediately at (831)
438-9550.
------------------------------------------
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
