X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SARE_HEAD_8BIT_SPAM,SARE_SUB_ENC_UTF8,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4FE42A0A.8070107@roularta.be> Date: Fri, 22 Jun 2012 10:17:14 +0200 From: "Gerard H. Pille" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120615 Firefox/13.0.1 SeaMonkey/2.10.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin unstable as hell on Windows7 =?UTF-8?B?NjRiaXTigI8=?= References: <4FE0596F DOT 4060702 AT roularta DOT be> <201206191631 DOT q5JGVSaD088723 AT barrierB241 DOT nike DOT com> <4FE33F15 DOT 50101 AT roularta DOT be> In-Reply-To: <4FE33F15.50101@roularta.be> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 As suggested, I did a "set CYGWIN=detect_bloda" before running cygwin.bat, but that didn't produce any output. It seems as if the shells are the most vulnerable. Quite often, working in vi, I get thrown out, with "You have running jobs". After a "^Jtty sane^J" and "fg", I can terminate vi almost normally. In most cases, X keeps running for a while. I've checked and double-checked: TMOUT isn't set. Shouldn't even matter, since I'm running vi. Thanks, Gerard -- 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