• 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: Scott Ribe <email@hidden>
  • Date: Mon, 26 Jan 2009 10:09:38 -0700
  • Thread-topic: How to catch and log EXC_BAD_ACCESS?

> Currently, the app just hangs and needs the user to send Force Quit to
> terminate the app.

You sure about that? It can take a while to prepare the crash report, and
during that time your app is certainly non-responsive. But that signal
causes the system to terminate your application, and I have ***NEVER*** seen
that termination fail, not under any circumstances. In fact, if the system
can't terminate the app after EXC_BAD_ACCESS, there would be no reason to
expect the user to be able to force quit it either...

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

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

  • Follow-Ups:
    • Re: How to catch and log EXC_BAD_ACCESS?
      • From: Michael Ash <email@hidden>
References: 
 >How to catch and log EXC_BAD_ACCESS? (From: Oleg Krupnov <email@hidden>)

  • Prev by Date: Re: Knowing when a NSArrayController is ready
  • Next by Date: autorelease problem
  • Previous by thread: Re: How to catch and log EXC_BAD_ACCESS?
  • Next by thread: Re: How to catch and log EXC_BAD_ACCESS?
  • Index(es):
    • Date
    • Thread