Bugs item #1608921, was opened at 2006-12-04 22:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1608921&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Threads Group: Python 2.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stephan R.A. Deibel (sdeibel) Assigned to: Nobody/Anonymous (nobody) Summary: PyThread_release_lock with pthreads munges errno Initial Comment: In normal operation with pthreads when PyThread_release_lock is called and it calls PyThread_acquire_lock in the "sanity check" errno will be set to 11 and left that way. It seems like this should not happen so thread switches don't arbitrarily and w/o much reason alter the program state. I ran into this working on a threaded debugger where a lock is used internally. The debugger I'm writing now saves/restores errno in its tracer but it seems like there is potential for this bug all over the place. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1608921&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
