Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Thu, 20 Apr 2000 17:45:22 -0400 From: Chris Faylor To: DJ Delorie Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Sigh. First cygwin show stopper? Message-ID: <20000420174522.A3446@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: Chris Faylor , DJ Delorie , cygwin-developers AT sourceware DOT cygnus DOT com References: <20000420173420 DOT A3286 AT cygnus DOT com> <200004202142 DOT RAA02338 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200004202142.RAA02338@envy.delorie.com>; from dj@delorie.com on Thu, Apr 20, 2000 at 05:42:08PM -0400 On Thu, Apr 20, 2000 at 05:42:08PM -0400, DJ Delorie wrote: >> I just discovered that, with my new signal handling scheme, it is not >> possible to trap things like SIGFPE and SIGSEGV on Windows 95. >> >> Does anyone think that this requires a new 1.1.1 release? > >Does it affect gdb, or just signal() ? Just signal. For some reason SIGSEGV seems to work correctly unless it's trapped. I really don't understand why. I've already checked in a patch to fix it. It was an extremely simple fix. This will affect people trying to configure libstdc++. I don't know how many other programs trap things like SIGSEGV and SIGFPE. cgf