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

Re: NSExceptionHandlerUncaughtSignalHandler


  • Subject: Re: NSExceptionHandlerUncaughtSignalHandler
  • From: Douglas Davidson <email@hidden>
  • Date: Thu, 10 Jul 2003 15:26:57 -0700

On Thursday, July 10, 2003, at 03:05 PM, Steve Gehrman wrote:

A few users report a problem where CPU usage goes really high and "sample" returns this...

I guess it has something to do with NSExceptionHandlerUncaughtSignalHandler, but I don't know what to do about this.

This is a known issue, having to do with a signal being generated inside the NSExceptionHandler handler. NSExceptionHandler signal handling has never been able to be 100% reliable--actually, due to the impossibility of knowing the full application state when the signal is raised, nothing that involves proceeding after a signal raise can be 100% reliable--but this goes beyond that, and causes problems even with signals that could have been caught. We're working on it.

Douglas Davidson
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >NSExceptionHandlerUncaughtSignalHandler (From: Steve Gehrman <email@hidden>)

  • Prev by Date: NSExceptionHandlerUncaughtSignalHandler
  • Next by Date: Using ObjectMalloc with gcc3.3/Xcode/etc: Does it work???
  • Previous by thread: NSExceptionHandlerUncaughtSignalHandler
  • Next by thread: Using ObjectMalloc with gcc3.3/Xcode/etc: Does it work???
  • Index(es):
    • Date
    • Thread