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 11:22:50 -0400 Message-ID: <20010912152250.23961.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20010912111825.A20965@redhat.com> (message from Christopher Faylor on Wed, 12 Sep 2001 11:18:25 -0400) Subject: Re: Quick testfeedback... References: <20010911230429 DOT A1898 AT redhat DOT com> <20010912012121 DOT A2889 AT redhat DOT com> <20010912132631 DOT 22619 DOT qmail AT lizard DOT curl DOT com> <20010912111825 DOT A20965 AT redhat DOT com> > Date: Wed, 12 Sep 2001 11:18:25 -0400 > From: Christopher Faylor > > And, it was hung where....? I don't know. Recall from my previous descriptions that once this bug hits us, we can't do anything with the hung processes -- attempts to kill them (except for "kill -9"), attach to them, etc. are ineffective. Which means that the only way to get any idea what's going on is to run the whole build under strace and hope that when the problem finally recurs, the strace output gives a suggestion of what's going on (but it didn't suggest anything useful to me). I've sent long strace logs to this list from when the problem has occurred in the past. See them for additional information. I have no reason to believe that the bug in its current manifestation is any different from its previous ones. jik