This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Sigh. First cygwin show stopper?
- To: DJ Delorie <dj at delorie dot com>
- Subject: Re: Sigh. First cygwin show stopper?
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Thu, 20 Apr 2000 17:45:22 -0400
- Cc: cygwin-developers at sourceware dot cygnus dot com
- References: <20000420173420.A3286@cygnus.com> <200004202142.RAA02338@envy.delorie.com>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
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