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: <2E300728EEF9D3119D8000E018C1864F5E42CA@gemini>
From: "Mortimer, Andy" <Andy DOT Mortimer AT software DOT aeat DOT com>
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: Thu, 5 Oct 2000 03:50:58 -0600 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Chris Faylor writes:
> >> On Tue, Sep 19, 2000 at 06:10:35PM +0100, Mortimer, Andy wrote:
> >> >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
> >> >> [...]
> >> > Now, I'm just left with the problem
> >> >of bash segfaulting inside Cygwin's signal handling thread ...  ;-)
[...]
> I've added some more code to the snapshots in an attempt to work
> around this problem.  I don't know if I was successful or not.

Using the 2000-Sep-29 snapshot seems to have changed 
something!  It does seem to be more reliable (it's always 
hard to tell with these things, but it only seems to have 
dumped once in this way since I installed the snapshot). 
I'll include the stackdump, but (partly because I've 
changed from using bash to ash  -- which doesn't 
exhibit this problem -- for some of the more important 
things) this now seems stable enough for me to use very 
successfully.  Thanks!  

I don't know if you want to take this any further or not; I
don't really know what the problem is that you're trying to
fix now, so I don't really know that I can do much more to
help!  I will certainly keep trying out any new snapshots if
this would help, or let me know if there's anything else I
can do, but short of coming up with a reproducible testcase
(which seems hard! )-: I'm stuck.

On which topic, what's the best forum for reporting bugs
in the snapshots?  The 2000-Sep-29 snapshot appears to
be unable to resolve through symlinks to directories with
trailing slashes, and although I suspect it's been found 
and fixed and is therefore not worth reporting, I can't 
access the CVS sources though our firewall to check, and 
there doesn't appear to be a later snapshot at the moment.

$ ln -s /bin dummy
$ ls dummy
[works]
$ ls dummy/
ls: dummy/: Not a directory
$ ls dummy/.
ls: dummy/.: Not a directory
$ ls dummy/cygwin1.dll
dummy/cygwin1.dll

Thanks,

Andy

-- 
Andy Mortimer, CFX Software Development
andy DOT mortimer AT aeat DOT com


Exception: STATUS_ACCESS_VIOLATION at eip=6100BA85
eax=610986C8 ebx=00000000 ecx=00000000 edx=00000001 esi=00000014 edi=61098740
ebp=048BFA08 esp=048BFCA8 program=C:\cygwin\bin\bash.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
048BFA08  6100BA85  (00000000, 00000000, 00000000, 00000000)
048BFCAC  6100BA85  (610986C8, 00000001, 77F88000, 77F60000)
048BFCDC  6100CB13  (00000001, 00000014, 048BFEFC, 0041BB04)
048BFDEC  6100D087  (00000014, 048BFEFC, 0041BB04, 00000000)
048BFF0C  6100D7DC  (00000014, 00000014, 00000000, 000001F4)
048BFF6C  61041F46  (00000000, 048BFFB8, 61004128, 048BFFB0)
048BFFB8  6100414A  (61092564, 00000000, 00000000, 61092564)
1570844 [sig] bash 315 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1604484 [sig] bash 315 handle_exceptions: Error while dumping state (probably corrupted stack)

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