There's a theory in QA'ing a program that says that the nature of the bugs you find are driven by the weaknesses of the development team. This can then lead you to predict where other, yet unknown, bugs are likely to be found.
Therefore the known bug you have discovered would indicate that the programmer(s) have left other, currently unknown, similar bugs in their code. And the occasional failures you see are most likely a consequence of those other bugs. Anyway, first fix the bugs you know about and then exhaustedly run your program through Gremlins to expose those other bugs you haven't found yet. They do exist! Roger Stringer Marietta Systems, Inc. (www.RF-TP.com) >From: Keith Rollin <[EMAIL PROTECTED]> > >Like I said, in practice, I don't really expect a crash to occur. If >you are having intermittent crashes, I would suspect another cause. > >I'm curious...are these intermittent problems occurring only on the >device? If not, I'm wondering how Poser could be changed to help you >out (whereas it currently doesn't seem to be). > >-- Keith Rollin >-- Palm OS Emulator engineer > > >At 6:21 PM -0500 2/12/03, Kevin OKeefe wrote: >>Please, let me be clear here: we DO NOT think that this is ok - it >>is a bug that WILL BE fixed. My problem is that the error is rare >>enough that fixing this and not seeing the problem for a month does >>not guarantee that this was the cause of the error we are seeing. I >>was hoping for some insight about how the mere reading of this value >>could destabilize the device and lead to a crash either immediately >>or later a fairly low percentage of the time. >> >> <SNIP> -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
