From: "Björn Stabel" <stabelweb@gmx.de>
To: cygwin@cygwin.com
Subject: ctrl-c doesn't reliably kill applications
Date: Mon, 14 Mar 2016 17:18:00 -0000 [thread overview]
Message-ID: <56E6F25A.7070000@gmx.de> (raw)
The ctrl-c shortcut doesn't reliably kill applications (anymore?).
It has been that way for at least a year now.
------------------------------------------------------------------------
One example is the ruby "rerun" tool (at least when used with a sinatra
app).
The problem can be reproduced using these steps:
1. Default cygwin install
2. Install rubygems package
3. gem install rerun sinatra
4. Make sure the rerun tool is in PATH (or specify the path to it
explicitly). I think rubygems installs executables from gems to
~/bin by default
5. rerun "ruby -e 'require(\"sinatra\")'"
6. ctrl-c
7. tasklist /fi "IMAGENAME eq ruby.exe"
* Expected: No process
* Actual: process is still running
You might have to repeat steps 5 to 7 a few times for the issue to occur.
Another problem is that Q sometimes doesn't exit rerun but only the app
running inside, but that might be a problem with rerun itself or with
the shutdown detection they use.
------------------------------------------------------------------------
Another example is Vagrant.
Although that is not a cygwin application, I usually recommend coworkers
to use it with cygwin, because it benefits from mintty's better console.
The problem there occurs when you invoke a long-running vagrant command
(vagrant provision, for instance) and then cancel it with ctrl-c.
If you do that, you're back at the bash prompt, but the provisioning run
still goes on and spams the console, making it unusable.
------------------------------------------------------------------------
Under Kubuntu Linux 14.04/kde/konsole/bash, neither of these problems exist.
What the two examples seem to have in common is that they're both one
application invoking another:
* rerun invokes sh -c "$1" (I think)
* vagrant provision invokes (its bundled?) ssh
I think this is a bug and should be fixed. Is the bug with Cygwin or
should I report it elsewhere?
- Björn Stabel aka. TomyLobo
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2016-03-14 17:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 17:18 Björn Stabel [this message]
2016-03-14 23:39 ` Kaz Kylheku
2016-03-15 0:46 ` ctrl-c doesn't reliably kill ping Frank Farance
2016-03-15 11:05 ` Andrey Repin
2016-03-15 11:43 ` Adam Dinwoodie
2016-03-16 14:46 ` cyg Simple
2016-03-16 4:56 ` Kaz Kylheku
2016-03-16 11:50 ` Andrey Repin
2016-03-16 14:51 ` cyg Simple
2016-03-16 15:57 ` Michael Enright
2016-03-16 17:33 ` Kaz Kylheku
2016-03-16 18:10 ` Lee
2016-03-17 21:10 ` Frank Farance
2016-03-17 21:29 ` Marco Atzeri
2016-03-15 15:13 ` Warren Young
2016-03-16 13:25 ` Marco Atzeri
2016-03-17 20:04 ` ctrl-c doesn't reliably kill applications Björn Stabel
2016-04-18 21:38 ` Aaron Digulla
2016-04-19 9:13 ` Corinna Vinschen
2016-04-19 16:30 ` Aaron Digulla
2016-03-16 16:07 ` ctrl-c doesn't reliably kill ping Lee
2016-03-16 16:50 ` Warren Young
2016-03-16 17:52 ` Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E6F25A.7070000@gmx.de \
--to=stabelweb@gmx.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).