Ross Ridge wrote: > Joe Seigh wrote: > >>Basically there's a race condition where an object containing the >>refcount can be deleted between the time you load a pointer to >>the object and the time you increment what used to be a refcount >>and is possibly something else but definitely undefined. > > > That doesn't really make sense. The object can't be deleted because > the thread should already have a reference (directly or indirectly) to > the object, otherwise any access to it can cause the race condition you > describe. >
True but if the thread didn't already have a reference, how would you get that initial reference to a shared object without a lock? -- Joe Seigh When you get lemons, you make lemonade. When you get hardware, you make software. -- http://mail.python.org/mailman/listinfo/python-list
