Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
Message-Id: <13179A03C694D211B84700105A1E6C8B2FCFCB@cfx-server.cfds.harwell.aeat.co.uk>
From: "Mortimer, Andy"
	 <andy DOT mortimer AT aeat DOT co DOT uk>
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
Date: Tue, 19 Sep 2000 18:10:35 +0100
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

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 ... ;-)

The stackdumps I'm getting are as included below, if it 
helps anybody (the stack trace itself is different each time, 
but the two lines I've prefixed with an asterisk are always 
the same).  As noted in a previous thread ("version 
2.04-1 of bash crashing", 25 August this year), it does 
seem to be inside the stack dumping code that it is giving 
this core, but more than that I'm not really qualified to 
tell. :-(  Is this a known bug?  If not, is there anything I 
can do to help debug it[1]?

Thanks,

Andy

[1] Much as I'd love to provide a useful, small test case, 
I can't find one. :-(  This seems to happen intermittently, 
in the course of running a large set of long and nested 
shell scripts, and I've so far failed to reduce it down to 
much less than an hour ... I noticed the other poster 
also mentioned "running 6 bash shells with scripts all 
at the same time."  I'll pass it on if I do!

-- 
Andy Mortimer, CFX-5 Architecture and Infrastructure Team
andy DOT mortimer AT aeat DOT com

*Exception: STATUS_ACCESS_VIOLATION at eip=6100922E
*eax=6107F7A8 ebx=6107F7A4 ecx=00000000 edx=00000000 esi=00000001 edi=0041BB04
ebp=1446F9F4 esp=1446FC94 program=C:\Cygwin\bin\bash.exe
*cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
1446F9F4  6100922E  (00000000, 00000000, 00000000, 00000000)
1446FCAC  6100922E  (6107F7A4, 00000001, 77F88000, 77F60000)
1446FCDC  6100A2A3  (00000001, 00000014, 1446FEFC, 0041BB04)
1446FDEC  6100A806  (00000014, 1446FEFC, 0041BB04, 00000000)
1446FF0C  6100AF00  (00000014, 00000014, 00000000, 000001F4)
1446FF6C  6103EE0E  (00000000, 1446FFB8, 610032F8, 1446FFB0)
1446FFB8  6100331A  (6107F440, 6174736E, 68536C6C, 6107F440)
1446FFEC  77F04EE8  (610032D0, 61082020, 77366377, 000003F3)
End of stack trace


[An automatic footer will be attached to this message.  By posting to a 
public mailing list, I implicitly give permission to read/disclose/copy
/delete/reply to/whatever the message.]


***********************************************************************
This transmission contains information which may be confidential and  
which may also be privileged.  It is intended for the named addressee  
only.  Unless you are the named addressee, or authorised to receive it 
on behalf of the addressee you may not copy or use it, or disclose it 
to anyone else.  If you have received this transmission in error please 
contact the sender.  Thank you for your cooperation. 
***********************************************************************

For more information about AEA Technology please visit our website at http://www.aeat.co.uk

AEA Technology plc registered office 329 Harwell, Didcot, Oxfordshire OX11 0QJ.
Registered in England and Wales, number 3095862.

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