On 12/7/2006 11:15 AM, Stephen Dodd wrote: > Since I started tracking crashes on our client base, I've found the > majority of my app crashes are not caught by the exception handler. That > is, the app will crash without invoking even the app level unhandled > exception event. > > Just about all the crashes that invoke the exception handler can be > traced back to my own code/behaviour errors. > > However for the ones that don't trigger the exception handler, I don't > know if it's because of my code, or a problem with the way REALbasic has > built the compiled app, or some system level glitch that killed the > app. What do you think? > > I write out all unusual activity to a log file and read it back in after > a crash and it almost never reports issues before an unhandled crash. > > Is it me? REALbasic? Or is it just IS and that's the life of apps.
I don't know what platform you're deploying on, but on Windows there is a way of injecting a structured exception handler that will catch the exceptions at the OS level and tell you whether the problem was in your code or in a dynamically loaded system or third party library. Naturally you'll get generic exceptions like "access violation", but they can still be useful. This approach won't rule out a compiler bug should the exception originate in your code, but it can still provide useful info in a number of scenarios. If you're using Windows and want to know more, let me know. If you're not, hopefully you can find a similar solution on your target platform. -- Charles Calvert Celtic Wolf, Inc. (703) 580-0210 [EMAIL PROTECTED] http://www.celticwolf.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
