X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4BFE52BD.3060205@gmail.com> Date: Thu, 27 May 2010 12:08:45 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: pty infinite master control thread spawning problem References: <4BF2A0A9 DOT 5070201 AT gmail DOT com> <20100526131100 DOT GJ10652 AT calimero DOT vinschen DOT de> In-Reply-To: <20100526131100.GJ10652@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 26/05/2010 14:11, Corinna Vinschen wrote: > I applied a patch to CVS. It worked for me, but while testing I > encountered a handle leak in your testcase and, naturally, I thought > it's my code. After some tinkering it turned out that your parent > process neglects to wait for the child process. Adding > > int status; > waitpid (child_pid, &status, 0); > > to the parent code removed the handle leak. Please test the change in > Cygwin if it fixes the original problem for you. Yes, everything is working fine now, thank you. (Sorry about the distraction over the handle leak, to create the testcase I had to sift through 1.6G of strace output to try and find the sequence of syscalls that triggered the problem and I guess I overlooked that aspect of it!) cheers, DaveK -- 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