From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41931 invoked by alias); 28 Aug 2019 20:33:31 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 41866 invoked by uid 89); 28 Aug 2019 20:33:31 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=BAYES_00,FROM_STARTS_WITH_NUMS,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=H*u:0.9.2, H*UA:0.9.2, HX-Languages-Length:1115, hear X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.12) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Aug 2019 20:33:29 +0000 Received: from kylheku.com ([70.79.163.252]) by shaw.ca with ESMTPA id 34dBiqItusAGk34dCiox0X; Wed, 28 Aug 2019 14:33:26 -0600 Received: from www-data by kylheku.com with local (Exim 4.72) (envelope-from <920-082-4242@kylheku.com>) id 1i34dB-00071H-58 for cygwin@cygwin.com; Wed, 28 Aug 2019 13:33:25 -0700 To: cygwin@cygwin.com Subject: Re: Bug report: Killing a native process may not actually kill it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Aug 2019 22:43:00 -0000 From: Kaz Kylheku <920-082-4242@kylheku.com> In-Reply-To: References: <20190828154553.GQ11632@calimero.vinschen.de> Message-ID: <893c47a5235335c035a83536ab3cd899@mail.kylheku.com> X-Sender: 920-082-4242@kylheku.com User-Agent: Roundcube Webmail/0.9.2 X-IsSubscribed: yes X-SW-Source: 2019-08/txt/msg00377.txt.bz2 On 2019-08-28 08:59, Quanah Gibson-Mount wrote: > --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen > wrote: >=20 >> Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only >> works reliably with Cygwin processes. There's >>=20 >> $ /bin/kill -f >>=20 >> to call the Win32 function TerminateProcess(pid) on a non-Cygwin >> process or an unresponsive Cygwin process. >=20 > As I noted, it was not unique to control-C. In any case, unfortunate > to hear that Cygwin will not address this issue. kill -f is clearly > not desirable for doing a clean shutdown of a process. Cygwin can't introduce Unix-like shutdown mechanisms (like the handling a non-fatal signal) into non-Cygwin processes which have no concept of that. It makes no sense. The Windows way to try to try to obtain a clean shutdown is to send a message to a window handle (WM_CLOSE or WM_QUIT or whatever); then if that fails, TerminateProcess rudely. kill shouldn't try to translate signals to window handle messages; it makes no sense. -- 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