| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
| Message-ID: | <9bbd2794050721014940f12467@mail.gmail.com> |
| Date: | Thu, 21 Jul 2005 01:49:41 -0700 |
| From: | Alex Goldman <alex DOT gman AT gmail DOT com> |
| Reply-To: | Alex Goldman <alex DOT gman AT gmail DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Ctrl-C not working as well as on Linux |
| Mime-Version: | 1.0 |
| X-IsSubscribed: | yes |
| X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id j6L8oDQn030362 |
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? -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |