From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13183 invoked by alias); 26 May 2011 19:31:42 -0000 Received: (qmail 13172 invoked by uid 22791); 26 May 2011 19:31:40 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from nm17-vm0.bullet.mail.bf1.yahoo.com (HELO nm17-vm0.bullet.mail.bf1.yahoo.com) (98.139.213.157) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Thu, 26 May 2011 19:31:21 +0000 Received: from [98.139.212.151] by nm17.bullet.mail.bf1.yahoo.com with NNFMP; 26 May 2011 19:31:20 -0000 Received: from [98.139.213.1] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 26 May 2011 19:31:20 -0000 Received: from [127.0.0.1] by smtp101.mail.bf1.yahoo.com with NNFMP; 26 May 2011 19:31:20 -0000 Received: from cgf.cx (cgf@173.48.46.160 with login) by smtp101.mail.bf1.yahoo.com with SMTP; 26 May 2011 12:31:20 -0700 PDT X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id A239242804D for ; Thu, 26 May 2011 15:31:19 -0400 (EDT) Date: Thu, 26 May 2011 19:31:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: help developing a good problem report Message-ID: <20110526193119.GA6015@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-05/txt/msg00403.txt.bz2 On Thu, May 26, 2011 at 12:10:27PM -0500, Rance Hall wrote: >I've been noticing an issue with cygwin that I find annoying and would >like to fix. > >Ive never submitted a cygwin problem report before so this is a first. > >My issue now is that I dont actually understand the problem well >enough to give a good report. > >Here is what is happening: > >I'm using mintty to run ssh and connect to a remote box. > >I shutdown the remote box. > >ssh client exits with error > >Mintty locks up and does not accept user input (no keystrokes) till >windows kills the session and it is restarted. > >Mintty does not lock up if I exit the remote ssh session properly >without a remote shutdown. > >Always reproducible on win 7 64bit host. > >How can I determine if the problem is ssh or mintty? > >What additional information is needed? For starters: |||||||||||||||||||||||||||||||||||||||||||||||||||||| VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV >Problem reports: http://cygwin.com/problems.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple