Re: Empty stack trace in crash reports
Re: Empty stack trace in crash reports
- Subject: Re: Empty stack trace in crash reports
- From: Greg Parker <email@hidden>
- Date: Tue, 21 Apr 2009 12:43:33 -0700
On 20 Apr 2009, at 21:49, Seth Willits wrote:
Alright, not strictly Cocoa related, but someone will surely know :)
What are the empty threads that show up in a crash report? ie Thread
22 crashed, and there's 20 threads listed in the report, but 17-21
have no stack trace. Is this a thread that hasn't started, hasn't
finished, is spazzed because of stack corruption?
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.
A thread with a bad PC or corrupt stack or highly optimized stack may
have an unintelligible stack trace, but it will always have at least
one entry with the current PC value.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
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