Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 15 Oct 2001 22:44:25 +0100
Message-ID: <7301-Mon15Oct2001224425+0100-starksb@ebi.ac.uk>
X-Mailer: 21.5  (beta2) "artichoke" XEmacs Lucid (via feedmail 9-beta-7 I);
	VM 6.92 under 21.5  (beta2) "artichoke" XEmacs Lucid
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.3.3-2 hangs on semaphore somewhere in NTDLL.DLL
In-Reply-To: <20011015144641.E6984@redhat.com>
References: <3BCB2D32 DOT 8050406 AT milohedge DOT com>
	<20011015144641 DOT E6984 AT redhat DOT com>

On Monday 15 Oct 01, Christopher Faylor writes:
> On Mon, Oct 15, 2001 at 07:38:42PM +0100, Robert Bogomip wrote:
> >  $ uname -a
> >  CYGWIN_NT-5.0 MACH 1.3.3(0.46/3/2) 2001-09-12 23:54 i686 unknown
> >
> >Right then. On my Win2000 (service pack 2) machine I've got two CPUs (733
> >Coppermines). Thus I often do "make -j 3" for fast builds. Unfortunately,
> >make often hangs on 1.3.3-2.  This appears to be a bug of 1.3.3-2 (i.e.,
> >it has always worked/continues to work with previous cygwin dll releases).
> 
> This problem was mentioned in the release announcement.

Do you mean this?

On Wednesday 12 Sep 01, Christopher Faylor writes:
> *** Known bugs:
> 
> - There is a very sporadic core-dumping situation that seems to be
>   best triggered by recursive makes.  We have not been able to track
>   down the cause of this problem after more than two weeks of trying.  So,
>   since it has been proven to be very rare, I'm releasing 1.3.3 with this
>   known problem.  If you can provide any insight on why this is happening
>   please send email with lots and lots of details to cygwin AT cygwin DOT com.
>   "Hey!  It dies for me too!" emails will not be helpful unless you provide
>   either an exhaustive amount of detail (stack trace, easily reproducible
>   test case, patch).  (Christopher Faylor)

This mentions a core-dump, Robert describes a hang.  Shall I add this
to the "relnotes" part of the FAQ, in the "known bugs" section?

David


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/