Re: Empty stack trace in crash reports
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 12:26:26 -0700
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 thread that hasn't started,
hasn't finished, is spazzed because of stack corruption?
I'm wondering if this could be a potential clue for some patterns
that I should be learning.
Are you using pthreads directly? If so, you either need to detach
your threads with pthread_detach() (or by creating them with an
attribute set by pthread_attr_setdetachstate()), or call
pthread_join(). If you don't do either, then you'll end up with
zombie threads in the same way that you do with processes.
Hmm. Nope. I'm only ever using NSThreads. Thanks for the thought.
--
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