This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: sig_send: wait for sig_complete event failed

To: "'cygwin at sources dot redhat dot com'" <cygwin at sources dot redhat dot com>
Subject: Re: sig_send: wait for sig_complete event failed
From: Chris Faylor <cgf at cygnus dot com>
Date: Mon, 18 Sep 2000 13:56:26 -0400
References: <13179A03C694D211B84700105A1E6C8B2FCFB3@cfx-server.cfds.harwell.aeat.co.uk>
Reply-To: cygwin at sources dot redhat dot com

On Fri, Sep 15, 2000 at 12:01:52PM +0100, Mortimer, Andy wrote:
>I've just bitten the bullet and upgraded from a b20.1 snapshot release to the 
>latest and greatest net release, and almost everything is much improved (so I 
>don't really want to go back ... ;-)  Unfortunately, I've started having various 
>problems with the error message:
>
>1184486202 [sig] bash 28849 sig_send: wait for sig_complete event failed, sig 11, rc 258, Win32 error 0

I don't know what is causing this but I can see that there is apparently
a SIGSEGV in cygwin's signal handling thread.

I've made a change to recent snapshots which will cause cygwin to core dump
in this situation rather than try to send a signal to itself which is never
caught.

If you have the time, please try out a snapshot.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Follow-Ups:
- Clearing NT Buffer
  - From: Matt Minnis

References:
- sig_send: wait for sig_complete event failed
  - From: Mortimer, Andy

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]