Re: Empty stack trace in crash reports
Re: Empty stack trace in crash reports
- Subject: Re: Empty stack trace in crash reports
- From: Alastair Houghton <email@hidden>
- Date: Tue, 21 Apr 2009 11:19:00 +0100
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?
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.
My guess is that that's what you're seeing here.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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