Message 78976 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	ebfe, gps, gregory.p.smith, pitrou, vstinner
Date	2009-01-03.17:08:37
SpamBayes Score	0.0018435667
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
I'm not sure about the approach of dynamically allocating self->lock. Imagine you allocate this lock while another thread is between ENTER_HASHLIB and LEAVE_HASHLIB. What happens on LEAVE_HASHLIB? The thread tries to release a lock it hadn't acquired (because the lock was NULL at the time). Is it simply ignored?

I'm not sure about the approach of dynamically allocating self->lock.
Imagine you allocate this lock while another thread is between
ENTER_HASHLIB and LEAVE_HASHLIB. What happens on LEAVE_HASHLIB? The
thread tries to release a lock it hadn't acquired (because the lock was
NULL at the time). Is it simply ignored?

History
Date	User	Action	Args
2009-01-03 17:08:38	pitrou	set	recipients: + pitrou, gregory.p.smith, vstinner, gps, ebfe
2009-01-03 17:08:38	pitrou	set	messageid: <[email protected]>
2009-01-03 17:08:38	pitrou	link	issue4751 messages
2009-01-03 17:08:37	pitrou	create