Mail Archives: cygwin-developers/2001/10/22/15:30:44

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 22 Oct 2001 15:30:36 -0400
Message-ID: <>
From: Jonathan Kamens <jik AT curl DOT com>
To: jik AT curl DOT com
CC: cygwin-developers AT cygwin DOT com
In-reply-to: <> (message from
Jonathan Kamens on 22 Oct 2001 15:24:30 -0400)
Subject: Re: 1.3.4 status?
References: <3BD4635D DOT 1060208 AT ece DOT gatech DOT edu> <20011022142729 DOT A10309 AT redhat DOT com> <20011022192430 DOT 3581 DOT qmail AT lizard DOT curl DOT com>

>  Date: 22 Oct 2001 15:24:30 -0400
>  From: Jonathan Kamens <jik AT curl DOT com>
>  >  Date: Mon, 22 Oct 2001 14:27:29 -0400
>  >  From: Christopher Faylor <cgf AT redhat DOT com>
>  >  
>  >  4) Jonathan Kamens says that cygwin core dumps for him.  Havne't
>  >     heard much about that. (jik)
>  I've been having trouble finding time to work on this, but I've been
>  working on it today.  What I've discovered so far is that it appears
>  to be related to the gcc flags used to compile Cygwin.  When I know
>  more I'll let you know.

The most recent snapshot doesn't exhibit this problem.  Therefore, you
shouldn't consider this a barrier to releasing 1.3.4 if the releases
are compiled with the same flags as the snapshots.  I'm continuing to


- Raw text -

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