Re: Obj-C runtime not thread-safe?!
Re: Obj-C runtime not thread-safe?!
- Subject: Re: Obj-C runtime not thread-safe?!
- From: Jean-Denis Muys <email@hidden>
- Date: Sat, 19 Jun 2004 15:15:54 +0200
I ran your little program on my Mac, and I can confirm the behaviour
you noticed: its output is fine in non-debug mode, while in debug mode,
the first time around, the thing class is nil.
This is on my Sawtooth Machine (PowerMac G4, AGP Graphics), 500 MHz,
one G4 processor, 1.12 GB RAM, XCode 1.5 beta, MacOS X 10.3.4.
I didn't try to understand why it misbehaves. You may want to file a
bug report.
Regards,
Jean-Denis
On Jun 18, 2004, at 4:51 PM, email@hidden wrote:
I have written a little sample program that will demonstrate this. Of
course, if you run it normally, the Thing class will initialize almost
instantly and the problem will not occur. But, at least on my G4/450
DP, running this in the debugger slows it down enough to make this
problem occur. Uncomment the first NSLog in Thing.m to see that one of
the threads isn't getting the class object.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.