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 amaury.forgeotdarc, ned.deily, neologix, thouis
Date 2011-12-01.22:41:53
SpamBayes Score 9.2503296e-07
Marked as misclassified No
Message-id <1322779314.66.0.638379025715.issue13517@psf.upfronthosting.co.za>
In-reply-to
Content
And here's a post by Ulrich Drepper:
http://udrepper.livejournal.com/18555.html

"""
readdir_r is only needed if multiple threads are using the same directory stream. I have yet to see a program where this really is the case. In this toy example the stream (variable dir) is definitely not shared between different threads. Therefore the use of readdir is just fine. Should this matter? Yes, it should, since readdir_r has to copy the data in into the buffer provided by the user while readdir has the possibility to avoid that.
"""

So I'm even more confident that we should keep the current code.
At least, before going any further (and complicating the code), I'd like to know whether this can be reproduced with a small C snippet.
History
Date User Action Args
2011-12-01 22:41:54neologixsetrecipients: + neologix, amaury.forgeotdarc, ned.deily, thouis
2011-12-01 22:41:54neologixsetmessageid: <1322779314.66.0.638379025715.issue13517@psf.upfronthosting.co.za>
2011-12-01 22:41:54neologixlinkissue13517 messages
2011-12-01 22:41:53neologixcreate