• 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: Tracking down SIGABRTs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tracking down SIGABRTs


  • Subject: Re: Tracking down SIGABRTs
  • From: Scott Ribe <email@hidden>
  • Date: Mon, 30 Apr 2012 13:17:03 -0600

On Apr 30, 2012, at 12:00 PM, Jens Alfke wrote:

> On Mac OS the system will also put up the standard crash alert, whereas a call to abort() (which is what assert() calls) just makes the app vanish with no explanation to the user.

Depends on the version perhaps? I certainly see abort() putting up the "The application has unexpectedly quit" dialog.

--
Scott Ribe
email@hidden
http://www.elevated-dev.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

References: 
 >Tracking down SIGABRTs (From: Alex Zavatone <email@hidden>)
 >Re: Tracking down SIGABRTs (From: Don Quixote de la Mancha <email@hidden>)

  • Prev by Date: Re: Tracking down SIGABRTs
  • Next by Date: Converting CGPathAddArcToPoint (or NSBezierPath equivalent) to a fixed number of CGPathAddCurveToPoint calls
  • Previous by thread: Re: Tracking down SIGABRTs
  • Next by thread: Re: Tracking down SIGABRTs
  • Index(es):
    • Date
    • Thread