X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3A9853940CFA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1614765401;
	bh=wmW81Z7A2zXiU9skW3jV0QCiyYv/SenypR55lL3bpNs=;
	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=BSGrFa/iNpEHX8mM66hCopoZKQFvUGxLe1qS/uE8ggIfCqdhOspMepKvFmL999ueQ
	 7EGgU6Cx3kduuO4A9p3FtBf09qXW2shhj3zWG8sMXQREqWmy4A0ScngrFcjD9p+acC
	 BuKXEwFsdav5TXx1EgQeE5M0vL3uS2qacK2Cwoys=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5C6CE384A02C
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 1239uJKK015866
X-Nifty-SrcIP: [118.243.85.178]
Date: Wed, 3 Mar 2021 18:56:21 +0900
To: cygwin AT cygwin DOT com
Subject: Re: segfault on 32bit cygwin snapshot
Message-Id: <20210303185621.b048287526901af6a4c8200a@nifty.ne.jp>
In-Reply-To: <YD5eXbxBWbUUSwcM@calimero.vinschen.de>
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>
 <YD5eXbxBWbUUSwcM AT calimero DOT vinschen DOT de>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-4.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.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>

Hi Corinna,

On Tue, 2 Mar 2021 16:48:45 +0100
Corinna Vinschen wrote:
> 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 <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?
> > > 
> > > 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.

I have checked all /usr/bin/*.dll in my cygwin installation and found
following dlls call uname() rather than uname_x().

/usr/bin/cyggcj-16.dll
/usr/bin/cyggstreamer-1.0-0.dll
/usr/bin/cygguile-17.dll
/usr/bin/cygguile-2.0-22.dll
/usr/bin/cyghwloc-15.dll
/usr/bin/cygLLVM-3.8.dll
/usr/bin/cygLLVM-3.9.dll
/usr/bin/cygLLVM-4.0.dll
/usr/bin/cygLLVM-5.0.dll
/usr/bin/cygLLVMSupport-3.7.dll
/usr/bin/cygoctinterp-7.dll
/usr/bin/cygpulsecommon-11.1.dll
/usr/bin/cygQt5Core-5.dll
/usr/bin/cygQt5WebKit-5.dll
/usr/bin/cygQtWebKit-4.dll
/usr/bin/cygslang-2.dll
/usr/bin/cygwebkitgtk-3.0-0.dll
/usr/bin/cygwx_baseu-2.8-0.dll
/usr/bin/libzsh-5.8.dll

I also confirm that the same problem occurs under cygwin snapshot
2021-02-22 if the following code is compiled with Qt5 because
this program is linked to /usr/bin/cygQt5Core-5.dll.

#include <QApplication>
#include <QLabel>
#include <QSysInfo>

int main(int argc, char **argv)
{
    QApplication app(argc, argv);
    QLabel *label = new QLabel(QSysInfo::kernelType());
    label->show();
    return app.exec();
}

Do you think rebuilding all of these (or maybe more) dlls is only
the solution? 

-- 
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