X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C50423AA991F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1614873152;
	bh=V1N6ApQ153oPtUXH8R0pW7CfeD+unsf7TG1dgsWz/JA=;
	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=RYzm+4gbsGQBjJijwRqMqNKIUYq3FFCa/rYa2qtmNF1fRBr1fVaJUfOAuzdUdIjSZ
	 oePfMe58f7vJPA187EY4brr8hnPRl4iRpD9ETlIQNdTeEV0L7XeptXPIdBMQ+FvBce
	 IL0NGIywtJG1yN/+Ruy/UhenZE116QIjMI6njUoA=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 088473AA9916
Date: Thu, 4 Mar 2021 16:52:23 +0100
To: cygwin AT cygwin DOT com
Subject: Re: segfault on 32bit cygwin snapshot
Message-ID: <YEECNwKsOiGM2YFX@calimero.vinschen.de>
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>
 <YD5eXbxBWbUUSwcM AT calimero DOT vinschen DOT de>
 <20210303185621 DOT b048287526901af6a4c8200a AT nifty DOT ne DOT jp>
 <YD9sSea32T7GqlJr AT calimero DOT vinschen DOT de>
 <20210304180534 DOT 7c3825e6ee989a2bf62f0652 AT nifty DOT ne DOT jp>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20210304180534.7c3825e6ee989a2bf62f0652@nifty.ne.jp>
X-Provags-ID: V03:K1:tOCEmflO0r6q0Hl8tCzLKoE+nx2FHN4v7iWntZu0PPMXJQfb43p
 /mcPc7bevHB+jnp7QgSwhvpqSSuV7bmnJkjkSR9+3IxAS2zQ7cVXZC88bNlRZebKhWuPObP
 onqghdNhYuhq3tqUBm9SGzLtlLKtcy/CeAZH134u0QduP3nR1HvCWpefTiJJ18zPyaCyivD
 +FDZIzJGO9c0CrM7q2eEg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:hw4qLALnXjg=:5SbfPnpDgBZY2YlGo7ki7l
 dmzzS0O44SYwSRnG9t44b2R+wgaPKmHdD0V1cxn4SV5qF5VNAxnzGxZ4ylE+tv95667aEKNXm
 LQp5W/edu5xWKRtINGJtJbBxw8J7GIlQJGJy6N1oGtBGPB/rQzdvcu9LjJnBerRWbf82zMDM8
 zBVnjyjR++GnAUKH3+A2xF+IGLQvleVFeNW9RntwuOZxq3Th6e7i1J702pB1us9t7t5vF5zZD
 sejlbxIWgOCBGgvHywucZ+Z4smvCToCRXMOfZ9XPr2ZluxHuOVhOUcQsBy1xOZKl/RoT6G/xN
 mkp5YYgTGvWlQrj+6Do9PtVNrpDW3S411/Pcls9bgunAgtWIJDqf5dJCdIi/RCKnk9KRkN8A1
 AUOV0YJgh2pw984dTkHVTQalpMecm/aaJVO5yYRF9bSTFqASkJ2BjlM5xu7OBY+CGZqiPhZdm
 r4aLzlGGHv19eaJrjT1FEycYEdxC3mDgSl+HPN1WS9kM2/o2u9XD1Z4Xqgva3Q9ce9iLOfVk3
 A==
X-Spam-Status: No, score=-101.1 required=5.0 tests=BAYES_00,
 GOOD_FROM_CORINNA_CYGWIN, JMQ_SPF_NEUTRAL, 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 <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: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
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 Mar  4 18:05, Takashi Yano via Cygwin wrote:
> Hi Corinna,
> 
> On Wed, 3 Mar 2021 12:00:25 +0100
> Corinna Vinschen wrote:
> > [Ping Mark Geisert]
> > 
> > Is there a way around that?  I'm not quite sure, so let's brain storm
> > a bit, ok?
> > 
> > - One thing we could try is to remove the above code, but add a python
> >   hack to dlsym instead.  This would let the "old" DLLs work again as
> >   before and for python we could add a hack to dlsym, along these lines:
> > 
> >     if (CYGWIN_VERSION_CHECK_FOR_UNAME_X
> >     	&& modulehandle == cygwin1.dll
> > 	&& strcmp (symname, "uname"))
> >       symname = "uname_x";
> > 
> > Thoughts?  Other ideas?
> 
> It sounds very reasonable to me to deal with it within dlsym(),
> as the problem arises from the use of dlsym(). However, what
> happens if newly built .exe is linked to old dll which calls
> uname() via dlsym()? I am not sure whether there are such dlls.

We simply can't fix that, because we don't have a Cygwin-specific
per-DLL information block as we have for EXEs.  There's no way to
workaround that problem.


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