Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 10 Jan 2002 16:57:27 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Am I using dumper.exe correctly?
Message-ID: <20020110215727.GB30469@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20020110214350 DOT 30413 DOT qmail AT lizard DOT curl DOT com> <048201c19a20$afd86530$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <048201c19a20$afd86530$0200a8c0@lifelesswks>
User-Agent: Mutt/1.3.23.1i

On Fri, Jan 11, 2002 at 08:49:31AM +1100, Robert Collins wrote:
>
>===
>----- Original Message -----
>From: "Jonathan Kamens" <jik AT curl DOT com>
>To: <cygwin-developers AT cygwin DOT com>
>Sent: Friday, January 11, 2002 8:43 AM
>Subject: Am I using dumper.exe correctly?
>
>
>> We're using cygwin-1.3.6-6 on our build servers and current versions
>> of just about all the other packages.  We get occasional crashes in
>> cygwin processes during our automated builds, so I decided to debug
>> them as follows:
>>
>> 1) Build the current CVS repository configured like this:
>>
>>    CFLAGS="-g -O" configure --enable-threadsafe \
>>      --enable-extra-threadsafe-checking --enable-debugging \
>>      --enable-vfork
>
>Hmm, I'm not sure that enable-threadsafe has any impact anymore, in 2000
>we removed some of the thread/non thread options - and looking closely I
>think that the removal wasn't as accurate as it could be. Anyway, I
>suggest not passing either thread option to cygwin.

I meant to mention that.  Maybe we should just nuke the options?
There's no way that cygwin will work in non-threadsafe mode anymore.

cgf