This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Bug: fhandler.cc rev=1.116 source code level bug in fhandler_base::dup (fhandler_base *child)
- From: mike stump <mrs at windriver dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 22 May 2002 14:27:16 -0700 (PDT)
- Subject: Re: Bug: fhandler.cc rev=1.116 source code level bug in fhandler_base::dup (fhandler_base *child)
- References: <20020522165921.GB3592@redhat.com>
> 1) What's "gmake"?
GNU make.
> 3) Why would anyone do a dup(dup(-1))?
Because they can. dup(-1) is defined to return -1, and otherwise not
do anything and set errno to EBADF.
> 4) Why would setting nh to anything affect this code? This code path is
> only invoked for /cygdrive or /proc style paths.
>
> If you have a specific problem, you should provide a test case. I don't
> see any problems with recursive invocation of gmake jobs with stdio.
compare:
( exec <&-; make foo; )
with
( exec <&-; make foo </dev/null; )
Makefile:
foo:
echo me
ls && echo me
This needs to work. When it works, one will see an ls, when it fails,
one will get a core file. On a real unix system (solaris for
example), it works just fine
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/