For the beta-testing purposes, I'd like my app to handle the situation when the EXC_BAD_ACCESS exception occurs, and treat it gracefully - i.e. send a crash report and perhaps terminate.
Currently, the app just hangs and needs the user to send Force Quit to terminate the app. I tried to wrap the problematic code with @try/@catch, but EXC_BAD_ACCESS seems to be a special kind of exception that is not trapped this way. Any advice is welcome! _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
