-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Alex Goldman on 7/21/2005 2:49 AM: > 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? >
What terminal are you using? If it is the Windows console, then you need to have CYGWIN=tty in your environment before starting bash to ensure saner behavior of Ctrl-C (at the expense of possibly breaking Windows native applications in the same console). See http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html#id4736242 or search some recent threads on the issue. Hint - following the problem reporting directions would have helped us know right off whether you were using the Windows console: > Problem reports: http://cygwin.com/problems.html - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC34/P84KuGfSFAYARAkGxAJ9JZA9vgGhft5+56OIG18T7NuFWlwCg2Ki/ 0syY90mkH1hE9tsnaoFvwFo= =tNiE -----END PGP SIGNATURE----- -- 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/
