Re: NSThread, NSAutoreleasePool and mach_trap_msg
Re: NSThread, NSAutoreleasePool and mach_trap_msg
- Subject: Re: NSThread, NSAutoreleasePool and mach_trap_msg
- From: Bill Bumgarner <email@hidden>
- Date: Wed, 18 Jun 2008 11:16:38 -0700
On Jun 18, 2008, at 11:10 AM, Georg Schuster wrote:
I'm sorry that I can't post any real code, but does anybody know if
there are some special things I should keep an eye on when
programming the WorkerClass? I tried to read every doc about threads
and autoreleasepools I could get my hands on (including the apple-
docs), but I just can't find any solution to get rid of that kernel
trap message.
In general, you don't subclass NSThread as you aren't overriding any
of its functionality, you are simply using an instance of it.
Instead, your worker class would use...
+ (void)detachNewThreadSelector:(SEL)selector toTarget:(id)target
withObject:(id)argument;
... to spawn a new thread.
I would fix that first and see if the problem continues. It may not.
b.bum
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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