This is the mail archive of the
mailing list for the Cygwin project.
Re: ctrl-c doesn't reliably kill applications
- From: Aaron Digulla <digulla at hepe dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 18 Apr 2016 23:38:27 +0200
- Subject: Re: ctrl-c doesn't reliably kill applications
- Authentication-results: sourceware.org; auth=none
- References: <56E6F25A dot 7070000 at gmx dot de> <56E75B3E dot 7020102 at farance dot com> <56E95EA2 dot 8070800 at gmail dot com> <56EB0DDE dot 60205 at gmx dot de>
On 17.03.2016 21:04, BjÃrn Stabel wrote:
> I couldn't replicate it either, but the question I started this thread
> with is unrelated to either of the ping tools.
> Here it is again:
> The ctrl-c shortcut doesn't reliably kill applications (anymore?).
> It has been that way for at least a year now.
I can confirm that. It's worse with native applications. In my case, I
have scripts which invoke Maven (a Java application).
Ctrl+C kills the script but the signal isn't forwarded to the Windows
process, so the Java process is stuck in the background.
To make matters worse, it tries to write to stdout which isn't properly
connected anymore. This can lead to Windows starting to trash the
harddrive until you have to turn off the computer.
Might be related to Ctrl+S/Ctrl+W handling as well (Unix kind of Scroll
Lock) which is also broken for native programs (you can freeze them but
Ctrl+W has no effect anymore until Windows freezes).
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple