Mail Archives: cygwin-developers/2002/01/10/16:49:35

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: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <048201c19a20$afd86530$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Jonathan Kamens" <jik AT curl DOT com>, <cygwin-developers AT cygwin DOT com>
References: <20020110214350 DOT 30413 DOT qmail AT lizard DOT curl DOT com>
Subject: Re: Am I using dumper.exe correctly?
Date: Fri, 11 Jan 2002 08:49:31 +1100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 10 Jan 2002 21:49:30.0600 (UTC) FILETIME=[AED65E80:01C19A20]

----- 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.


> 1) Things run Very Slowly with the new version of cygwin1.dll.  If I
>    had to guess, I'd guess that --enable-extra-threadsafe-checking is
>    probably the culprit.  Can anybody confirm or deny that?

The overhead shouldn't be that significant, but try it without and see
for yourself :}.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019