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 4F6BA3894438 for ; Mon, 1 Mar 2021 11:26:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4F6BA3894438 Received: from Express5800-S70 (y085178.dynamic.ppp.asahi-net.or.jp [118.243.85.178]) (authenticated) by conssluserg-05.nifty.com with ESMTP id 121BQLtU020126 for ; Mon, 1 Mar 2021 20:26:21 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 121BQLtU020126 X-Nifty-SrcIP: [118.243.85.178] Date: Mon, 1 Mar 2021 20:26:22 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: segfault on 32bit cygwin snapshot Message-Id: <20210301202622.1f880e6392f49f2a67c50ddc@nifty.ne.jp> In-Reply-To: <20210301174157.5727974b3dabe31810eb3994@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> <20210301174157.5727974b3dabe31810eb3994@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: Mon, 01 Mar 2021 11:26:47 -0000 On Mon, 1 Mar 2021 17:41:57 +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? > > I looked into this deeper a bit. > > Perhaps, lilypond passes old small sized utsname structure to > uname() via old cygguile-17.dll (built on Apr. 2017). This seems > to cause stack destruction. So, I guess rebuilding and replacing cygguile-17.dll will solve the issue. However, I am not sure whehter the new binary works with cygwin 3.1.7. -- Takashi Yano