X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DEC5B3842418
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1614560158;
	bh=mhBkzj4oHQ54h5IHUaRv1bi9u9ffFvOcPiWIbxJSsPc=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=DBWdv18i3MMFUW+PV5bLLsQ5EhdQoDWoqI2hEW3eGooInFJ9Zw7PACDf8NKSH4gd9
	 eV7p1x0wEEE8jtS7VhMfE23pY6/6kWCK5PaH/C3xb10nfKkxpxzpOisP+uZXBUP0Qz
	 oXwNzXF2qyfcztw1lhiDaGNrJsXKwbx2v3+avKjs=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A5F323857C56
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 1210taJv014840
X-Nifty-SrcIP: [118.243.85.178]
Date: Mon, 1 Mar 2021 09:55:46 +0900
To: cygwin AT cygwin DOT com
Subject: Re: segfault on 32bit cygwin snapshot
Message-Id: <20210301095546.dce31a474bd0cec2c3518f87@nifty.ne.jp>
In-Reply-To: <7480c946-8e02-aba2-c06f-6b39f630699f@gmail.com>
References: <9d7b9dc2-cb92-498b-7655-e9c618114c87 AT gmail DOT com>
 <20210221072954 DOT db2dcbd523ed366e4dfcb0d0 AT nifty DOT ne DOT jp>
 <7480c946-8e02-aba2-c06f-6b39f630699f AT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-4.3 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 AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

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 <corinna AT vinschen DOT de>
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 <corinna AT vinschen DOT de>

Reverting this commit solves the issue.

Corinna, could you please have a look?

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
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