Re: Killing a Thread
Re: Killing a Thread
- Subject: Re: Killing a Thread
- From: Mahaboob <email@hidden>
- Date: Thu, 27 Nov 2008 16:52:55 +0530
- Thread-topic: Killing a Thread
Thanks for your valuable comments.
The thread is not exit and now it working for another threads.
I used one progress window to display the delivery progress of the mail.
When I'm calling the thread for second time, the animation speed of progress
bar get increased. And also some times I'm getting the error like:
objc[2568]: FREED(id): message sendMessage sent to freed object=0x5eba400
Thanks
Mahaboob
On 11/26/08 10:50 PM, "Scott Ribe" <email@hidden> wrote:
> It occurs to me that maybe you do not know about or understand the use of
> the pause button in the debugger.
>
> Get your application to the state where it's hung up. Then hit the pause
> button in the debugger. Then use the thread popup to examine the stack of
> each thread. Once you know where each thread is locked up, you should have a
> much better chance of figuring out the problem.
>
> Note that there may be threads you don't expect--this is normal as the
> frameworks sometimes create their own threads for their own background
> processing. You should at first ignore threads not running any of your code.
_______________________________________________
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