X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 27 May 2010 15:39:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: pty infinite master control thread spawning problem Message-ID: <20100527133923.GB14645@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4BF2A0A9 DOT 5070201 AT gmail DOT com> <20100526131100 DOT GJ10652 AT calimero DOT vinschen DOT de> <4BFE52BD DOT 3060205 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4BFE52BD.3060205@gmail.com> 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 May 27 12:08, Dave Korn wrote: > 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 [...] > > 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!) No worries. As long as it allows to reproduce the problem with a minimum of code, better a slightly flawed testcase than no testcase at all. 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