Message 138774 - 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	neologix
Recipients	greg.ath, neologix
Date	2011-06-21.09:47:53
SpamBayes Score	0.0011155417
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to	<[email protected]>

Content
> The obvious solution is to use a recursive lock instead. Note that it's not really a solution, just a workaround to avoid deadlocks, become this might lead to a corruption if free is called while the heap is in an inconsistent state. I have to think some more about a final solution, but I'd like to check first that this is really what's happening here.

> The obvious solution is to use a recursive lock instead.

Note that it's not really a solution, just a workaround to avoid
deadlocks, become this might lead to a corruption if free is called
while the heap is in an inconsistent state. I have to think some more
about a final solution, but I'd like to check first that this is
really what's happening here.

History
Date	User	Action	Args
2011-06-21 09:47:54	neologix	set	recipients: + neologix, greg.ath
2011-06-21 09:47:54	neologix	link	issue12352 messages
2011-06-21 09:47:53	neologix	create