• 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: Making failed NSAsserts crash an app
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making failed NSAsserts crash an app


  • Subject: Re: Making failed NSAsserts crash an app
  • From: Graham Cox <email@hidden>
  • Date: Thu, 27 Aug 2009 10:04:56 +1000


On 27/08/2009, at 10:00 AM, Rob Keniger wrote:

You could raise exceptions instead of generating assertion failures. Exceptions are caught by several of the crash reporting frameworks. You could probably map the NSAssert macros to exception-generation code for your beta builds.


The NSAssert macros raise exceptions by default in debug builds.

--Graham


_______________________________________________

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: Making failed NSAsserts crash an app
      • From: Squ Aire <email@hidden>
References: 
 >Making failed NSAsserts crash an app (From: Squ Aire <email@hidden>)
 >Re: Making failed NSAsserts crash an app (From: Rob Keniger <email@hidden>)

  • Prev by Date: Re: How to Convert "#FF00FF" String Specifying RGB Color to 32 bit int
  • Next by Date: Re: How to Convert "#FF00FF" String Specifying RGB Color to 32 bit int
  • Previous by thread: Re: Making failed NSAsserts crash an app
  • Next by thread: RE: Making failed NSAsserts crash an app
  • Index(es):
    • Date
    • Thread