Re: Empty stack trace in crash reports

2009-04-21 Thread Seth Willits
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 h

Re: Empty stack trace in crash reports

2009-04-21 Thread Greg Parker
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 t

Re: Empty stack trace in crash reports

2009-04-21 Thread Seth Willits
On Apr 21, 2009, at 3:19 AM, Alastair Houghton 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 t

Re: Empty stack trace in crash reports

2009-04-21 Thread Alastair Houghton
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 th

Empty stack trace in crash reports

2009-04-20 Thread Seth Willits
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 spazze