Regression: (was Re: Ctrl-C not working as well as on Linux)

2005-07-28 Thread Linda W
Christopher Faylor wrote: 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

Re: Ctrl-C not working as well as on Linux

2005-07-21 Thread Igor Pechtchanski
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)",

Re: Ctrl-C not working as well as on Linux

2005-07-21 Thread Alex Goldman
My tty settings are fine. I run Rxvt by calling C: chdir C:\cygwin\bin set CYGWIN=codepage:oem tty binmode title rxvt -sl 1000 -e bash --login -i Looking into this more closely, I noticed that the problem occurs for programs compiled using the free MSVC++ Toolkit 2003, but not GCC. I think you

Re: Ctrl-C not working as well as on Linux

2005-07-21 Thread Christopher Faylor
On Thu, Jul 21, 2005 at 06:06:39AM -0600, Eric Blake wrote: >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 Cygwi

Re: Ctrl-C not working as well as on Linux

2005-07-21 Thread Eric Blake
-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 >

Ctrl-C not working as well as on Linux

2005-07-21 Thread Alex Goldman
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