X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Thu, 26 May 2011 12:10:27 -0500 Message-ID: Subject: help developing a good problem report From: Rance Hall To: "(Unknown)" Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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? Thanks, Rance -- 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