X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_CG,TW_YG X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1//cYsiVIljxl7Mfun8ldAs Date: Mon, 19 Mar 2012 16:54:33 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin-1.7.10-1 fork - address space needed by ... already in use Message-ID: <20120319205433.GA5571@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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> <20120308095535 DOT GT5159 AT calimero DOT vinschen DOT de> <20120309154829 DOT GA31351 AT ednor DOT casa DOT cgf DOT cx> <20120316171426 DOT GA20243 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120316171426.GA20243@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Fri, Mar 16, 2012 at 01:14:26PM -0400, Christopher Faylor wrote: >On Fri, Mar 09, 2012 at 10:48:30AM -0500, Christopher Faylor wrote: >>On Thu, Mar 08, 2012 at 10:55:35AM +0100, Corinna Vinschen wrote: >>>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. >> >>I have a vague idea about why this is happening. I'll look into it within >>the next 48 hours. > >My vague idea about this proved to be incorrect. I did manage to make a >royal mess of the exec synchronization code before I figured that out >though so at least that's something. > >Denis, did you see this while running the STC in > >http://cygwin.com/ml/cygwin/2012-02/msg00187.html > >? > >Also, I checked back through the archives but didn't see any cygcheck >output from you. Maybe I just missed it but would you mind sending it >here? > >To see if I could duplicate this, I created a STC which rapidly forked a >bunch of processes which also execed themselves. I could never get this >error to show up though. Thanks for the cygcheck output. I was never able to duplicate the problem so I rewrote the way this was handled. The error message is completely gone now. With luck you won't see anything like this now. cgf -- 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