Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <18cb01c19f0d$6d6d37b0$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <18c301c19f0c$7176a770$0200a8c0 AT lifelesswks> <20020117041203 DOT GA5805 AT redhat DOT com> Subject: Re: tty and the cygwin server Date: Thu, 17 Jan 2002 15:14:15 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 17 Jan 2002 04:15:14.0266 (UTC) FILETIME=[90040BA0:01C19F0D] === ----- Original Message ----- From: "Christopher Faylor" > >My question is, what occurs between accept_input and > >process_slave_output in rxvt that could result in ash (the slave) > >quitting? I can't get a strace of the slaves behaviour so far, which is > >why I'm turning for inspiration here... > > Probably it is looking like stdin (the pty) is being closed for some > reason. That seems to be what's happening from the strace. Or it has > received a signal? You should be able to attach to the process via gdb > and watch it happen. Thanks. I had similar thoughts, but couldn't say why that would occur. Rob