• 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: Crash Reporter for Cocoa Application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash Reporter for Cocoa Application


  • Subject: Re: Crash Reporter for Cocoa Application
  • From: Scott Ribe <email@hidden>
  • Date: Fri, 16 Nov 2007 09:58:55 -0700
  • Thread-topic: Crash Reporter for Cocoa Application

> Polling the crash report file is both wasteful and unnecessary when
> you have kernel events, and launchd already provides a mechanism for
> firing off a program when a file changes.

Yes, I'm aware of that--it's why I haven't posted the code publicly and
announced "look everybody, a non-intrusive way to get crash reports". The
current thing is more prototype quality, implemented in Ruby, and has
another problem in addition to the polling: possibility of a race condition
on rapid app re-launch causing the crash log monitoring to not run.

--
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

References: 
 >Re: Crash Reporter for Cocoa Application (From: Nicko van Someren <email@hidden>)

  • Prev by Date: Re: NSMenuItem target binding
  • Next by Date: Re: CoreImage problems with very large images
  • Previous by thread: Re: Crash Reporter for Cocoa Application
  • Next by thread: NSClipView leaves background artifacts when drawing
  • Index(es):
    • Date
    • Thread