Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 <cgf AT cygnus DOT com>
Date: Wed, 11 Oct 2000 13:27:27 -0400
To: cygwin-developers AT sources DOT redhat DOT com
Subject: Re: Cygwin exiting mysteriously
Message-ID: <20001011132727.A11411@cygnus.com>
Reply-To: cygwin-developers AT sources DOT redhat DOT com
Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com
References: <20001011171648 DOT 1170 DOT qmail AT web106 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: <20001011171648.1170.qmail@web106.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Oct 11, 2000 at 10:16:48AM -0700

On Wed, Oct 11, 2000 at 10:16:48AM -0700, Earnie Boyd wrote:
>--- Chris Faylor <cgf AT cygnus DOT com> wrote:
>> 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?
>> 
>
>No, there was no visible output, the process, i.e. the bash command window,
>just exited.  I don't know if it printed logout, it exited immediately after
>the return.
>
>Ok.  I'll see what I can do with an strace from a cmd.exe window starting bash.
> It'll be a little while getting, I've work to do.

Hey!  What kind of lame excuse is that?  :-)

Anyway, thanks for the additional details.  This gives me something to
mull over.  It looked like ls was actually doing the right thing, but
silently.  Very strange.

cgf