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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, fabioz
Date 2008-08-18.21:06:37
SpamBayes Score 1.787632e-06
Marked as misclassified No
Message-id <1219093599.61.0.315263869623.issue3494@psf.upfronthosting.co.za>
In-reply-to
Content
I could reproduce the problem, and it appears that it is the same as
#1608818, corrected by r65037:

on posix platforms, listdir() used to check for errno only at the end of
the list; the problem is that the trace function creates a thread, and
this sets errno (harmlessly) somewhere when playing with locks.

In the python codebase, every function that checks errno should set it
to zero before the system call.
The above fix could be backported.

As a workaround, I suggest to put a line like 
   int('0')
near the end of the trace funtion (at least after the creation of the
thread) because it has the nice side-effect to reset errno.
History
Date User Action Args
2008-08-18 21:06:39amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, fabioz
2008-08-18 21:06:39amaury.forgeotdarcsetmessageid: <1219093599.61.0.315263869623.issue3494@psf.upfronthosting.co.za>
2008-08-18 21:06:38amaury.forgeotdarclinkissue3494 messages
2008-08-18 21:06:37amaury.forgeotdarccreate