From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-01.nifty.com (conssluserg-01.nifty.com [210.131.2.80]) by sourceware.org (Postfix) with ESMTPS id 88B9F3858034; Tue, 2 Mar 2021 11:03:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 88B9F3858034 Received: from Express5800-S70 (y085178.dynamic.ppp.asahi-net.or.jp [118.243.85.178]) (authenticated) by conssluserg-01.nifty.com with ESMTP id 122B36dH006839; Tue, 2 Mar 2021 20:03:08 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 122B36dH006839 X-Nifty-SrcIP: [118.243.85.178] Date: Tue, 2 Mar 2021 20:03:08 +0900 From: Takashi Yano To: cygwin@cygwin.com Cc: corinna-cygwin@cygwin.com Subject: Re: segfault on 32bit cygwin snapshot Message-Id: <20210302200308.62db4fe01f78fb35a538784f@nifty.ne.jp> In-Reply-To: <20210301212542.8b1749f92af62c01b008f25a@nifty.ne.jp> References: <9d7b9dc2-cb92-498b-7655-e9c618114c87@gmail.com> <20210221072954.db2dcbd523ed366e4dfcb0d0@nifty.ne.jp> <7480c946-8e02-aba2-c06f-6b39f630699f@gmail.com> <20210301095546.dce31a474bd0cec2c3518f87@nifty.ne.jp> <20210301212542.8b1749f92af62c01b008f25a@nifty.ne.jp> 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=-4.2 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.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.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: , X-List-Received-Date: Tue, 02 Mar 2021 11:03:29 -0000 On Mon, 1 Mar 2021 21:25:42 +0900 Takashi Yano wrote: > On Mon, 1 Mar 2021 09:55:46 +0900 > Takashi Yano wrote: > > On Sun, 28 Feb 2021 19:48:28 +0100 > > Marco Atzeri wrote: > > > On 20.02.2021 23:29, Takashi Yano wrote: > > > > On Sat, 20 Feb 2021 22:01:38 +0100 > > > > Marco Atzeri wrote: > > > >> MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10) > > > >> > > > >> now fails at startup with > > > >> > > > >> Exception: STATUS_ACCESS_VIOLATION at eip=61083736 > > > > > > > > Thanks for the report. I found the cause of this issue. > > > > I will submit a patch to fix it. > > > > > > > > > > mc is now fine with 2021-02-22 > > > > > > but I found another issue > > > > > > $ /usr/bin/lilypond > > > GNU LilyPond 2.20.0 > > > Segmentation fault (core dumped) > > > > > > on 3.1.7 it works fine > > > > I found this problem causes after the commit: > > > > commit 532b91d24e9496c7988b2b1dda7fc0e8b161f782 > > Author: Corinna Vinschen > > Date: Mon Dec 14 12:29:23 2020 +0100 > > > > Cygwin: Make sure newer apps get uname_x even when loading uname dynamically > > > > if an application built after API version 334 loads uname dynamically, > > it actually gets the old uname, rather than the new uname_x. Fix this by > > checking the apps API version in uname and call uname_x instead, if it's > > a newer app. > > > > Signed-off-by: Corinna Vinschen > > > > Reverting this commit solves the issue. > > > > Corinna, could you please have a look? > > The following check code does not work as expected if > newly build exe file is linked with old dll which calls > uname() as in this case. > > if (CYGWIN_VERSION_CHECK_FOR_UNAME_X) > return uname_x (in_name); > > Any idea? Ping Corinna? -- Takashi Yano