On 12/21/11 23:54, Joachim Schmitz wrote: > The code path you modified is not touched at all.
Oh well, it was a bit of a stab in the dark anyway. I guess we'll have to do Eric's suggestion to wrap opendir <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10305#68>. That should work around the problem, and in some sense it's nicer anyway because it causes dirfd to work in the usual way (as required in the next POSIX).