From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: catching SIGSEGV
31 Dec 1998 13:24:01 -0800
Message-ID: <Pine.SUN.3.93.981231145827.29298A-100000.cygnus.cygwin32.developers@modi.xraylith.wisc.edu>
References: <19981231145005 DOT A19955 AT cygnus DOT com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Christopher Faylor <cgf AT cygnus DOT com>
Cc: cygwin32-developers AT cygnus DOT com, DJ Delorie <dj AT cygnus DOT com>

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.

Regards,
Mumit