From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 91077 invoked by alias); 3 Sep 2019 05:38:24 -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 91070 invoked by uid 89); 3 Sep 2019 05:38:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=survived, enjoys, citizen, HX-Received:8c01 X-HELO: mail-io1-f54.google.com Received: from mail-io1-f54.google.com (HELO mail-io1-f54.google.com) (209.85.166.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 03 Sep 2019 05:38:22 +0000 Received: by mail-io1-f54.google.com with SMTP id m11so1181693ioo.0 for ; Mon, 02 Sep 2019 22:38:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Qy935Ql833SSd74QiyUvJ/B8hwD8YO617RJuRuj7b+4=; b=jhmxsaiQ4d0brF0hV4RQhvcr1+eBGr1NBfS9lr9xY3l/Stjbm/b9yK0T7IEuID82wn 1s0LU/wKncF0B1S+ewKdZREo+CCAErN3UcNVaZvRw4YpxkFRUnVHA2X/iAEEqSK+Lzf7 rtO7Un7bXObaBmKvQ8WA1MAjBLlL6E1aY9ixn7JvY3QUKynF8foexRx5BhLgVV2x2Jlo 75Lsmq6IhooxlM5srM6Mp8/9Jml9UoJFxVZihSdzH9tZLem/6rEQWjFinzz5j+321l7A zYrD/dZj0Xfu+4RGEU2dAZpuWo2a82KIsOHlW8EMlCKjfYvZ/VnIMZyIXLjc3WKKNZ0k /33A== MIME-Version: 1.0 References: <5d671e60.1c69fb81.eba3d.1ef8@mx.google.com> In-Reply-To: <5d671e60.1c69fb81.eba3d.1ef8@mx.google.com> From: Ray Donnelly Date: Tue, 03 Sep 2019 05:38:00 -0000 Message-ID: Subject: Re: Bug report: Killing a native process may not actually kill it To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00011.txt.bz2 On Thu, 29 Aug 2019, 02:38 Steven Penny, wrote: > On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote: > > My original post contained a link to a patch allowing for Cygwin to > > correctly terminate native Windows processes. I understand it is not > the > > position of the Cygwin project to deal with situation, so I think we can > > just let it drop. > > I would like to say that I support this, if it can be done in a reasonable > way. > > Ive been reading this thread carefully, and Ive yet to see anyone comment > on the > merits of the patch. Apologies if Ive overlooked it. > > To me, the first and only question that matters is "does it solve more > problems > than it causes". If the answer is yes, I think the patch should be > accepted. > Else I think its unfair to prematurely end the discussion. > > Cygwin has a long history of... putting Cygwin first. I dont mean this as a > negative, although I do disagree with the sentiment. Any compiling is with > Cygwin target as first class citizen, then native Windows has always been > an > afterthought. I think this is why the MinGW survived as long as it did, and > while the MSYS2 project enjoys the popularity it has today. With MSYS2, the > "Cygwin" mode is still primary, but you can launch "mingw64.exe" and native > Windows becomes the default. > We can consider the patch at msys2 also if you wish to propose it. > > If Cygwin wishes to remain insular in regard to this and other native > Windows > issues, thats their choice. It does make development significantly easier I > assume. However I think in doing so it alienates significant portion of the > userbase. > > > -- > 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 > > -- 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