Dr. Hawkins wrote:
I've been living through the frequent random crashes...
Computers are deterministic systems: consistent inputs will yield
consistent results.
If something may appear to be random, it merely suggests we haven't
found the recipe for reproducing it yet.
All problems with computers can be resolved by identifying the
differences between the working and non-working states.
Your filing a bug report is helpful (#14350 for those wishing to help
triage this), but the crash log may not be enough for the team to
identify what went wrong.
It might, though, and if so then we have nothing more to worry about.
But if this issue is important to you (and it would seem that it is),
you may be able to get what you want more easily by including in your
bug report a description of what your program is doing when it crashes.
If this is really important, you may consider adding some script logging
to your stack so you can at least know the last handler that executed
successfully.
If you haven't yet played with the messageMessages property and the
messageHandled message to make such a log, I can provide a simple script
for you to log all handler calls to a text file.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
