Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 21 Jul 2005 12:16:14 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: Alex Goldman cc: cygwin@cygwin.com Subject: Re: Ctrl-C not working as well as on Linux In-Reply-To: <9bbd2794050721014940f12467@mail.gmail.com> Message-ID: References: <9bbd2794050721014940f12467@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 21 Jul 2005, Alex Goldman wrote: > On Linux, after I start a program that consumes 100% of CPU time, I > can usually terminate it just by typing Ctrl-C. This is very > convenient to me as a developer. However, using Cygwin in the same > situation, the shell becomes "bash (Not Responding)", and I have to > invoke the process manager and kill the process from there. Does > anyone know why this happens and what can be done about it? Must be a Windows (non-Cygwin) program. Ctrl-C should still work, but it would be interesting to strace the bash that invokes the program to see what happens on Ctrl-C. FYI, if you know the PID (cf "top"), you could use "/bin/kill -f WINPID" to achieve the same effect as the task manager's "End process" button. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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/