Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Tue, 19 Sep 2000 13:40:26 -0400
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
Message-ID: <20000919134026.A29858@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: "'cygwin AT sources DOT redhat DOT com'" <cygwin AT sources DOT redhat DOT com>
References: <13179A03C694D211B84700105A1E6C8B2FCFCB AT cfx-server DOT cfds DOT harwell DOT aeat DOT co DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <13179A03C694D211B84700105A1E6C8B2FCFCB@cfx-server.cfds.harwell.aeat.co.uk>; from andy.mortimer@aeat.co.uk on Tue, Sep 19, 2000 at 06:10:35PM +0100

On Tue, Sep 19, 2000 at 06:10:35PM +0100, Mortimer, Andy wrote:
>Hi Chris/list,
>
>Chris Faylor writes:
>>On Fri, Sep 15, 2000 at 12:01:52PM +0100, Mortimer, Andy wrote:
>>>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.
>
>As noted in another message, the latest snapshots didn't work for me,
>but I've applied just the patch referred to here and it has indeed
>stopped the hang.  Thanks, Chris! Now, I'm just left with the problem
>of bash segfaulting inside Cygwin's signal handling thread ...  ;-)

Are you saying that you took the changes from the snapshot, applied them
to 1.1.4 sources, and rebuilt a DLL?

Unfortunately, I can't decipher a snapshot if you're using a home grown
DLL unless you're willing to tell me what all of the 6100* addresses
resolve to symbolically.

For that you can use 'addr2line' or gdb.

Btw, the argv[0] problem should be fixed in the next snapshot.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com