X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 8 Mar 2012 10:55:35 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin-1.7.10-1 fork - address space needed by ... already in use
Message-ID:	<20120308095535.GT5159@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20120208090824 DOT GA1724 AT qp9482> <20120208092711 DOT GF25129 AT calimero DOT vinschen DOT de> <20120208102235 DOT GA2796 AT qp9482> <20120304172210 DOT GI18852 AT calimero DOT vinschen DOT de> <20120305070927 DOT GA2396 AT qp9482> <20120305095919 DOT GO18852 AT calimero DOT vinschen DOT de> <20120305120230 DOT GA6624 AT qp9482> <20120305121436 DOT GR18852 AT calimero DOT vinschen DOT de> <20120307174749 DOT GB19570 AT calimero DOT vinschen DOT de> <20120308085029 DOT GA9588 AT qp9482>
MIME-Version:	1.0
In-Reply-To:	<20120308085029.GA9588@qp9482>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Mar  8 09:50, Denis Excoffier wrote:
> On Wed, Mar 07, 2012 at 06:47:49PM +0100, Corinna Vinschen wrote:
> >> Hi Denis,
> >> 
> >> can you please test this again using the latest developer snapshot or
> >> the current from CVS if you build Cygwin by yourself?  It provides a bit
> >> more information to find the reason for the permission denied error in
> >> _pinfo::dup_proc_pipe.
> Thank you cgf (the committer and snapshot maker at least).
> >> 
> >> In theory, the user should have permissions to duplicate handles into
> >> every own process, if the handle has been opened with these permissions,
> >> so it's quite interesting to find the reason.
> >> 
> 
> After about 3 hours of exercising the new snapshot (and shaking it a
> little), i met the "something failed" instance only twice:
> 
>       1 [main] tcsh 7648! _pinfo::dup_proc_pipe: (child_info_spawn::worker) process synchronization failed for pid 7648/0x754, wr_proc_pipe 0x0 vs. 0x764: DuplicateHandle winerr 5, WFSO returned 258, Win32 error 5
>     503 [main] tcsh 6148! _pinfo::dup_proc_pipe: (child_info_spawn::worker) process synchronization failed for pid 6148/0x758, wr_proc_pipe 0x0 vs. 0x768: DuplicateHandle winerr 5, WFSO returned 258, Win32 error 5
> 
> I continue, of course.

Thanks, I don't think it's necessary to try further.  What this shows is
that the process handle returned by the call to CreateProcess sometimes,
for some reason, does not allow handle duplication.  That's weird.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -