Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Empty stack trace in crash reports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Empty stack trace in crash reports

Subject: Re: Empty stack trace in crash reports
From: Seth Willits <email@hidden>
Date: Tue, 21 Apr 2009 14:31:59 -0700

On Apr 21, 2009, at 12:43 PM, Greg Parker wrote:

If the stack trace is truly empty - not even a single address in the list - then they're probably idle workqueue threads. They're part of the NSOperation implementation, the kernel adds or deletes them whenever it feels like, and they don't have any backtrace when they're not executing something.

Ahhhh. That's all it is then. I figured every thread would have at least one entry.


Thanks Greg,

--
Seth Willits

_______________________________________________

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:  
  >Empty stack trace in crash reports (From: Seth Willits <email@hidden>)
  >Re: Empty stack trace in crash reports (From: Alastair Houghton <email@hidden>)
  >Re: Empty stack trace in crash reports (From: Seth Willits <email@hidden>)
  >Re: Empty stack trace in crash reports (From: Greg Parker <email@hidden>)




Prev by Date:
Re: Getting the message text of a mail

Next by Date:
GSM 7 bit NSString?

Previous by thread:
Re: Empty stack trace in crash reports

Next by thread:
Problem in displaying image in NSTableView

Index(es):

Date
Thread