From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Quanah Gibson-Mount <quanah@symas.com>
Cc: cygwin@cygwin.com
Subject: Re: Bug report: Killing a native process may not actually kill it
Date: Wed, 28 Aug 2019 15:59:00 -0000 [thread overview]
Message-ID: <20190828154553.GQ11632@calimero.vinschen.de> (raw)
In-Reply-To: <DA9B3D3B0A3DE3E5A4720981@[192.168.1.144]>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Aug 28 08:18, Quanah Gibson-Mount wrote:
>
>
> --On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount
> <quanah@symas.com> wrote:
>
> > As found and reported to the MSYS team back in 2006 by Howard Chu, if a
> > native process is spawned, control-C, the kill command, etc, may not
> > actually kill the process. Details are here:
>
> I haven't seen a reply to this, so I just wanted to confirm that the Cygwin
> project is aware and (hopefully) will be able to do something to fix this in
> the long term.
Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only
works reliably with Cygwin processes. There's
$ /bin/kill -f <PID>
to call the Win32 function TerminateProcess(pid) on a non-Cygwin
process or an unresponsive Cygwin process.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-28 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 17:32 Quanah Gibson-Mount
2019-07-25 18:30 ` openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it) Achim Gratz
2019-07-25 19:04 ` openldap on Cygwin Quanah Gibson-Mount
2019-08-28 15:46 ` Bug report: Killing a native process may not actually kill it Quanah Gibson-Mount
2019-08-28 15:59 ` Corinna Vinschen [this message]
2019-08-28 16:02 ` Quanah Gibson-Mount
2019-08-28 20:33 ` Corinna Vinschen
2019-08-28 22:43 ` Kaz Kylheku
2019-08-29 0:02 ` Quanah Gibson-Mount
2019-08-29 1:01 ` Steven Penny
2019-09-03 5:38 ` Ray Donnelly
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=20190828154553.GQ11632@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=quanah@symas.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).