Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: mike stump <mrs AT windriver DOT com>
Date: Wed, 22 May 2002 14:27:16 -0700 (PDT)
Message-Id: <200205222127.OAA23136@kankakee.wrs.com>
To: cygwin AT cygwin DOT com
Subject: Re: Bug: fhandler.cc rev=1.116 source code level bug in fhandler_base::dup (fhandler_base *child)
References: <20020522165921 DOT GB3592 AT redhat DOT 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/