Yes, I do that, take a look at the "main" method in the code I attached. The errors seem to be coming from the GNUstep NSOperationQueue code, as I can spawn a thread to run the code without getting the error.
Scott On Nov 23, 2010, at 1:36 AM, Sašo Kiselkov wrote: > Concurrent operations run in separate threads, which don't automatically > create autorelease pools (which are thread-local). You should enclose code > which runs in a separate thread always in a new autorelease pool. > > -- > Saso > > On 11/23/2010 12:44 AM, Scott Christley wrote: >> >> Hello, >> >> I'm trying to use NSOperationQueue to run a bunch of concurrent operations. >> I used the bit of sample code from the Apple documentation for the basic >> structure, but the code prints some errors and hangs on GNUstep. Does >> anybody know what the problem might be? >> >> I get this from my program on GNUstep, it hangs after doing one operation. >> >> >> 2010-11-22 18:39:29.080 testOperation[3487] autorelease called without pool >> for object (0x199b060) of class GSKVOInfo in thread <NSThread: 0x191c4e0> >> 2010-11-22 18:39:29.082 testOperation[3487] autorelease called without pool >> for object (0x199b060) of class GSKVOInfo in thread <NSThread: 0x191c4e0> >> starting >> ending: 10000000001.000000 >> >> >> I'm using gnustep-startup-0.25.0 on 64-bit ubuntu. Threads seem to be >> working just fine. >> >> thanks >> Scott >> >> >> _______________________________________________ >> Discuss-gnustep mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/discuss-gnustep > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnustep
_______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
