X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4A1923858D28 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 2410pXRw008875 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1651366293; bh=WNjrUmPVjtZixOJ5pxRFO0V/BJkcd7eZHw3ERNvU8Lo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=B8VVin+UcRh0Zdz6OynCk+LaxrswvG38hUeTpbMxSa8ZqVpC0B4nvMY64DDBWFfH1 Yt2yki4GWI+USB0iWw8g46AopWsJHRJguNGS+9vto5yLLAEUqB2mdM0yUmRhRdkCOw JMbIHLezDqRDeD3zJiEHnWekD3nu2K+fIGYRf1F+NDsd+1RBH9DFREfkmqQ83zhdwO iIro9mx7Ov7sHbhkPIa8SM4Urr4L8dxGPURk2TNn1N3+XJtABrh+Iqt1wSf4PWoHCB xzJUgF4DeJnPLNGz1zDsTQqXlUdGockF+Xa0fUhmmKIZsV8UduydxoGEfrDNFfmKWj LnGX69N8wbTGQ== X-Nifty-SrcIP: [119.150.44.95] Date: Sun, 1 May 2022 09:51:41 +0900 From: Takashi Yano To: cygwin AT cygwin DOT com Subject: Re: GNU make losing jobserver tokens Message-Id: <20220501095141.b7e39c9f08e413d49aa4fdc2@nifty.ne.jp> In-Reply-To: References: <9b9da583-124d-9d5f-4c10-6622602ca8dc AT oracle DOT com> <20220401174551 DOT 820cbc148852554108397e03 AT nifty DOT ne DOT jp> <20220427231340 DOT 0bdab2d6d903dd4fb44bd12f AT nifty DOT ne DOT jp> <20220429000152 DOT 1fe838469e543a69586e194d AT nifty DOT ne DOT jp> <20220429181010 DOT 01940adc0cdbabf976997a6a AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Sat, 30 Apr 2022 17:51:03 -0400 Ken Brown wrote: > On 4/29/2022 5:10 AM, Takashi Yano wrote: > > On Thu, 28 Apr 2022 17:32:22 +0200 > > I tried to move sigproc_init() call from dll_crt0_0() to > > fork::child() for 64bit cygwin, however, that causes hang > > at cygwin startup. > > > > Am I missing somehting? > > I've never looked into the Cygwin startup code, so just ignore me if what I say > is nonsense. > > Currently sigproc_init is called either from dll_crt0_0 or from dll_crt0_1, > depending on the value of dynamically_loaded. What would happen if you always > call it from dll_crt0_1, right after > > cygwin_finished_initializing = true; Thanks for the advice. That causes hang on cygwin startup due to fork() fail :( -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple