Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 5 Jan 2005 20:40:26 -0800 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: problems interrupting cygcheck -c on 20050104 snapshot Message-ID: <20050106044026.GB2100@efn.org> References: <20050106021410 DOT GA4068 AT efn DOT org> <20050106040513 DOT GA7317 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050106040513.GA7317@trixie.casa.cgf.cx> User-Agent: Mutt/1.4.1i Organization: bs"d X-IsSubscribed: yes On Wed, Jan 05, 2005 at 11:05:13PM -0500, Christopher Faylor wrote: > On Wed, Jan 05, 2005 at 06:36:02PM -0800, Yitzchak Scott-Thoennes wrote: > >Using the 20050104 snapshot, running cygcheck -c from bash in a > >console window with tty set and hitting control-C or kill'ing the > >process (from another window) results in a burst of garbage to the > >screen, and cygcheck -c continues on. > > Can't duplicate it. Sorry. Rats. It doesn't happen in rxvt or without tty. > There hasn't been any changes in signal handling in some time so I don't > know why this snapshot should behave differently than any of the previous > snapshots. > > Were you seeing the same behavior in previous snapshots? Don't know, but will check. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/