Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: 12 Sep 2001 09:26:31 -0400 Message-ID: <20010912132631.22619.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20010912012121.A2889@redhat.com> (message from Christopher Faylor on Wed, 12 Sep 2001 01:21:21 -0400) Subject: Re: Quick testfeedback... References: <20010911230429 DOT A1898 AT redhat DOT com> <20010912012121 DOT A2889 AT redhat DOT com> > Date: Wed, 12 Sep 2001 01:21:21 -0400 > From: Christopher Faylor > > (Who's fully prepared for the fact that Jonathan will now get gdb > running and will provide a stack trace to the "make segvs" problem that > has been haunting us, causing me to delay the release *again* while we > try to fix it) I laughed when I read this ;-). Alas, I have not yet duplicated the problem, because the looping build test I started last night before going to sleep hung with the "make -j2" problem we've been seeing (you know which one I mean :-). I have (a) rebuilt cygwin1.dll against the current CVS repository (updated a few minutes ago), (b) confirmed that my error_start setting is working properly by using the test that you described, and (c) restarted my looping build test. We'll see if I can catch this bug in action and do some debugging. jik