From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-05.nifty.com (conssluserg-05.nifty.com [210.131.2.90]) by sourceware.org (Postfix) with ESMTPS id AD3FC3858D34 for ; Thu, 28 May 2020 01:32:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org AD3FC3858D34 Received: from Express5800-S70 (v038192.dynamic.ppp.asahi-net.or.jp [124.155.38.192]) (authenticated) by conssluserg-05.nifty.com with ESMTP id 04S1WFra007452 for ; Thu, 28 May 2020 10:32:15 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 04S1WFra007452 X-Nifty-SrcIP: [124.155.38.192] Date: Thu, 28 May 2020 10:32:18 +0900 From: Takashi Yano To: cygwin-developers@cygwin.com Subject: Re: 'nohup' seems to be broken in Cygwin git master Message-Id: <20200528103218.d39d580615e211bb05b13493@nifty.ne.jp> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2020 01:32:33 -0000 On Wed, 27 May 2020 17:47:41 -0700 (PDT) Mark Geisert wrote: > Easiest way I have to reproduce is using X. In a Cygwin terminal enter: > nohup xlogo & > exit > > The terminal window and xlogo are both terminated. With gdb I see that > xlogo terminates with STATUS_CONTROL_C_EXIT. > > On a 32-bit 3.1.4 install, same machine, same (64-bit 3.1.pre5) X server, > the same test case shows the terminal window terminated but xlogo remains. > > X is not required to demonstrate this; it's just easiest way to see the > effect. I can dig further if this doesn't immediately pique someone's > interest... :) Thanks for the report. This issue seems to occur after commit 7659ff0f5afd751f42485f2684c799c5f37b0fb9. I will submit a patch for this issue shortly. -- Takashi Yano