• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to catch and log EXC_BAD_ACCESS?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to catch and log EXC_BAD_ACCESS?


  • Subject: Re: How to catch and log EXC_BAD_ACCESS?
  • From: Ken Thomases <email@hidden>
  • Date: Wed, 28 Jan 2009 03:06:53 -0600

On Jan 26, 2009, at 5:33 AM, Oleg Krupnov wrote:

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.

You might look into NSExceptionHandler, which can do something somewhat useful on the way to terminating your app. Although, really, letting Crash Reporter collect the report is probably better. And, as discussed, EXC_BAD_ACCESS/SIGSEGV should lead to terminating your app.


Regards,
Ken

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >How to catch and log EXC_BAD_ACCESS? (From: Oleg Krupnov <email@hidden>)

  • Prev by Date: Re: Binding Buttons and Popup Menus to NSDictionary made from a prefs plist?
  • Next by Date: Re: Is there a more efficient way to get the first 4 bytes off a NSInputStream to compare
  • Previous by thread: Re: How to catch and log EXC_BAD_ACCESS?
  • Next by thread: Full screen on a display other than the main display
  • Index(es):
    • Date
    • Thread