From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: catching SIGSEGV
31 Dec 1998 13:31:56 -0800
Message-ID: <19981231160043.A20952.cygnus.cygwin32.developers@cygnus.com>
References: <19981231145005 DOT A19955 AT cygnus DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Mumit Khan <khan AT xraylith DOT wisc DOT edu>
Cc: cygwin32-developers AT cygnus DOT com, DJ Delorie <dj AT cygnus DOT com>

On Thu, Dec 31, 1998 at 02:59:43PM -0600, Mumit Khan wrote:
>On Thu, 31 Dec 1998, Christopher Faylor wrote:
>> There is no reason for GCC to avoid catching a SIGSEGV.  This must be
>> a holdover from some ancient cygwin.
>
>Thanks. I've made the change in my copy of egcs-1.1.1.
>
>> I don't know why cygwin is producing a window rather than a "core dump".
>> That's strange behavior.
>
>That was my good. The bug report had said cygwin, but really meant mingw
>(and rectified in a later message). Sorry about that.

That's ok.  DJ just reported the same behavior with Cygwin.

cgf