Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3BD05521.276D0035@syntrex.com>
Date: Fri, 19 Oct 2001 18:30:25 +0200
From: Pavel Tsekov <ptsekov@syntrex.com>
Organization: Syntrex Inc.
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: simple execvp test
References: <3BCECA31.4FE7AAD2@syntrex.com> <20011018171144.B19399@redhat.com> <3BCFF639.B4F5CF47@syntrex.com> <3BCFFB48.1E2B85F7@syntrex.com> <20011019121704.B26429@redhat.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:
> 
> On Fri, Oct 19, 2001 at 12:07:04PM +0200, Pavel Tsekov wrote:
> >Pavel Tsekov wrote:
> >>
> >> I'm looking at the spawn_guts code to see if
> >> there is something in this setup which may
> >> broke execvp.
> >>
> >
> >Btw I found something which may broke spawn_guts,
> >though I dont think this is the case with
> >James - see below:
> >
> >This code is from spawn_guts - the interesting thing
> >about it is that it doesn set the errno (__seterrno())
> >if the DuplicateHandle doesnt succeed. All the other
> >Win32 apis which a called though the spawn_guts set
> >the errno if they fail.
> >
> >So if we have execvp which loops through the PATH while
> >it finds the executable thus executing spawn_guts many
> >times most of which it fails with ENOENT and if spawn_guts
> >fail to duplicate handle the errno will still be set to
> >ENOENT which is not correct, maybe :)
> >
> >  if (!DuplicateHandle (hMainProc, hMainProc, hMainProc,
> >&ciresrv.parent, 0, 1,
> >                        DUPLICATE_SAME_ACCESS))
> >     {
> >       system_printf ("couldn't create handle to myself for child, %E");
> >       return -1;
> >     }
> 
> Did you see this error message?  If not, why are you mentioning this
> code?
> 

Huh .. At the top of the message I say i suppose it has nothing to
do with the problem which started this thread. I thought it may break
things however in the more general case - so I reported it - aside from
the execvp problem.

So this is how it should be ?

--
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/