Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 25 Feb 2000 20:15:57 -0500 To: Matt Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: 2/24 snapshot problems Message-ID: <20000225201557.B3484@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <20000225111450 DOT C31323 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i In-Reply-To: ; from matt@use.net on Fri, Feb 25, 2000 at 02:56:05PM -0800 On Fri, Feb 25, 2000 at 02:56:05PM -0800, Matt wrote: >On Fri, 25 Feb 2000, Chris Faylor wrote: > >> On Fri, Feb 25, 2000 at 12:35:18AM -0800, Matt wrote: >> >I just tried out the 2/24 snapshot, and I can't do anything without it >> >freezing/exiting on me. Output is below. Anyone have different results? >> > >> >"C:/Cygwin/bin/bash.exe"-2.03$ uname -a >> >CYGWIN_NT-4.0 D00R4N 1.1.0(0.16/3/2) 2000-02-25 00:15:29 i586 unknown >> > 0 0 [sig] C:\Cygwin\bin\bash.exe 1000 sig_send: wait for >> >sig_complete event failed, sig 11 >> >, rc 258, Win32 error 0 >> > 0 16714056 [unknown (0xB7)] bash 1000 sig_send: wait for sig_complete event failed, sig 2, rc 25 8, Win32 error 0 >> >> Do you have a stackdump file or strace output? > >sorry, strace log is attached (gzip'd cuz it was kinda big). This seems to be a "hanging" problem rather than the SIGSEGV you show above. I have made a few more changes to the signal logic. Please try out the next snapshot and let me know if it helps or hurts. cgf