Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!ukma!tut.cis.ohio-state.edu!osu-cis!att!cbnews!lml
From: lml@cbnews.ATT.COM (L. Mark Larsen)
Newsgroups: comp.bugs.sys5
Subject: Re: libPW.a(curdir.o) [SVR3.0+]
Message-ID: <5322@cbnews.ATT.COM>
Date: 2 Apr 89 07:00:36 GMT
References: <5226@cbnews.ATT.COM> <461@fciva.FRANKLIN.COM>
Reply-To: lml@cbnews.ATT.COM (L. Mark Larsen)
Organization: AT&T Bell Laboratories
Lines: 19

In article <461@fciva.FRANKLIN.COM> dag@fciva.UUCP (Daniel A. Graifer) writes:
#Has this been fixed in more recent releases?  I don't have source but we are
#about to move from SVR3.0 to 3.1.  It would be nice if this were fixed.  I am
#also about to buy a new 386 machine with 3.2.  What about that release?

(I tried mailing this but it bounced.)
As near as I can determine, SVR3.1 has the same bug.  I don't have the SVR3.2
source although I do have the source for the compiler (4.2) that comes with
3.2 and it has the bug too (sources for libraries are part of the compiler
package).  So, I wouldn't count on it being fixed anytime soon.  Of course,
as was pointed out, there are other alternatives.  If you are writing something
that would use this function, I suppose you could work around the bug by
explicitly closing the (n + 1)th file descriptor known to be in use, right
after the call to curdir().

cheers,
L. Mark Larsen
lml@atlas.ATT.COM
att!atlas!lml