Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Mon, 18 Sep 2000 13:56:26 -0400 To: "'cygwin@sources.redhat.com'" Subject: Re: sig_send: wait for sig_complete event failed Message-ID: <20000918135626.A4367@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: "'cygwin@sources.redhat.com'" References: <13179A03C694D211B84700105A1E6C8B2FCFB3@cfx-server.cfds.harwell.aeat.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <13179A03C694D211B84700105A1E6C8B2FCFB3@cfx-server.cfds.harwell.aeat.co.uk>; from andy.mortimer@aeat.co.uk on Fri, Sep 15, 2000 at 12:01:52PM +0100 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