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 sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: Chris Faylor Date: Wed, 11 Oct 2000 12:58:20 -0400 To: cygwin developers Subject: Re: Cygwin exiting mysteriously Message-ID: <20001011125820.A11082@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygwin developers References: <20001011162248 DOT 15325 DOT qmail AT web120 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001011162248.15325.qmail@web120.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Oct 11, 2000 at 09:22:48AM -0700 On Wed, Oct 11, 2000 at 09:22:48AM -0700, Earnie Boyd wrote: >I've a strace.gz attached which shows that the process kills itself. I could >only get this to happen with another process executing a huge build (Cygwin). I don't see anything strange in this strace. Was there no output from ls? It certainly thought it was outputting stuff. I see a standard kill_pgrp, called by do_exit. This causes everything in the process group to be sent a SIGHUP if the process is the process group leader. In this case, AFAICT, nothing was killed, which is what I would expect. From the strace it looks like ls went through all of the proper initialization code, then read the current directory, then displayed it. That's probably not what actually happened, though? cgf