Re: dup(0) failed after 3195 successes: Bad file descriptor

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Tue, Jun 29, 2004 at 10:10:18AM -0400, Tom Lane wrote:
>> Hmm. What system is this on? What errno code corresponds to
>> "Bad file descriptor"?

> That would be EBADF I think. However, my linux manpage indicates it's
> not a possible return from dup, only from dup2. Very odd.

HPUX man page says that it's a valid dup() error when the *supplied*
descriptor is bogus. Which is surely not true for zero (stdin) and
is even less plausible given that the previous 3195 iterations of this
tight loop had no problem with the same supplied descriptor.

But CSN says in a followup that this is on Cygwin. In short, what we
got here is another Cygwin bug [yawn]. I'm inclined to do something
like

if (thisfd < 0)
{
/*
* Expect EMFILE or ENFILE, else it's fishy; and Cygwin has
* a fishiness level all of its own...
*/
if (errno != EMFILE && errno != ENFILE
#ifdef __CYGWIN__
&& errno != EBADF
#endif
)
elog(WARNING, "dup(0) failed after %d successes: %m", used);
break;
}

unless someone can point to another platform that does the same thing.
(Hey -win32 hackers: does the native port exhibit this behavior?)

regards, tom lane