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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 20 Jan 2002 22:10:30 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: interrupt failure after upgrading 1.3.6-6 to 1.3.7-1 Message-ID: <20020121031030.GB22374@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <001901c1a20b$a3e1aaa0$6d7b1f3e AT leper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001901c1a20b$a3e1aaa0$6d7b1f3e@leper> User-Agent: Mutt/1.3.23.1i On Sun, Jan 20, 2002 at 11:39:01PM -0000, fergus at bonhard dot uklinux dot net wrote: >> ls -lR seems to terminate just fine with CTRL-C. > >Yes, worked for me too in this case. > >> 'cygcheck -r -s -v' might help track this down. > >Thanks for this suggestion. I tried 'cygcheck -r -s -v' under each regime. >The resulting screeds are very similar (and very long) and wonder whether >you would at least take a look at the difference between them. (It looks >utterly unexceptionable to me. But I don't know what to look for.) As >follows: I wasn't asking you to track things down by looking at cygcheck -r -s -v. I was saying that you should post your results. That's kinda the whole point with cygcheck -r -s -v. Regardless, the other person who responded to this thread, who sent in the output, gave me the clue that I needed. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/