X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 263FC39484B0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1614700130; bh=OV7NtBIh49D5ObnyvoK0ATDU89XzXfPT5LJw+/I7zW0=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=NyZ4osxzqvo0XTGaCCAJhlbZthlaFFk7l1x9f59xTvjyq3h0uSJHnga2up62OBSbn b8qHGTJK1cdEy1IoXKHWDbvykdrKev/+Crx7yxle4z4Z3cD0GEtU44XImN+skSXMyN wp2B7Q1tvZqJhz4NEJhpQwk+OGJF8kLYYwJehTQ8= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A7E9A3861026 Date: Tue, 2 Mar 2021 16:48:45 +0100 To: cygwin AT cygwin DOT com Subject: Re: segfault on 32bit cygwin snapshot Message-ID: Mail-Followup-To: cygwin AT cygwin DOT 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> <20210301095546 DOT dce31a474bd0cec2c3518f87 AT nifty DOT ne DOT jp> <20210301212542 DOT 8b1749f92af62c01b008f25a AT nifty DOT ne DOT jp> <20210302200308 DOT 62db4fe01f78fb35a538784f AT nifty DOT ne DOT jp> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20210302200308.62db4fe01f78fb35a538784f@nifty.ne.jp> X-Provags-ID: V03:K1:u4uagDW7uROtsGqOu7FLSc+GO4MrqGwLaKs3EPB2nwn4jImzXLH ka/ROwatSSli4t/4WUBShUoM7GCCXyyf+2qTE0OMH4PtI2X9vbsfI47atsQSwNkMK237dgu GFO7NLtPc3sMroHpRXhF5systXSvNUGtu1a4RxAFfTdbJlsrEAs3haLlw0mg6jcrIY6oSNz mebMo2nZrEnHA/Jol1S4A== X-UI-Out-Filterresults: notjunk:1;V03:K0:WVKTcOS+4Gw=:dvZK221cWc9UaxKSdAn1W1 ydcQklIM8aicrJhbMloToTBKFF7p55lSkbH27BkRfy6B/Jtkraw+jajixKW+pPCHaQslpmc8J 4UnGGrpXW8xqQrP8EgrvsmZsRjagfHIoDbo8Rl6y8WWEPckERGmlJY4tCPCwBLtz1lgkZc3dK SSSY8umC7Jy7fRkdw5VKmB8rlsfIyh+gB6dPgN7aMEKW04zUVT0b+NS+l03e3Zkz87GqBmo0e N2S5stV/VDUNAjjnsmpnSI4rWaywsMpOTimvTU9vIx7yeGUYVXgQu1y0wofmal1Z0rb53b7V5 FXyx6ps+UQQABHjWhUp5b2r1K+AgQeVERdn5sdFvp27HEvbZr8nhTmDlJ3h2YUw+gh977k+sc ZwctXV5P2dThjy2uSvQgtJB0WAXL06enkxqRwoPzsrU5sSSiSinBHTKwxCJViUReFzG/uRG6D 6oYNjZhIDg== X-Spam-Status: No, score=-101.4 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On Mar 2 20:03, Takashi Yano via Cygwin wrote: > 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? I have no idea how we could fix that, other than by rebuilding the DLLs which call uname, too. We can't check the Cygwin build of all DLLs an executable is linked to. Corinna -- 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