X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 69646382E801
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1614858630;
	bh=VA4r8dcTtuSG1VA9t25yZKp39GzpfvG0ncozghCrq10=;
	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=kBRnDr7y/4+/LxRstC5hxznL6+YbqxhQ4HqyFe+hN3AQ7pdgecwSHPH7pAd0JMNU+
	 EuOSGviiYnEMITHS2kMb5T1iVwAOiK1GTpWHMbPObs+q+eg064kECC03cted740AR5
	 Hh91V1PBnhOK29v6TVu+MFEGSgAimMcqBIalzL7Y=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0FAA63840C0C
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 124Bnxav028161
X-Nifty-SrcIP: [118.243.85.178]
Date: Thu, 4 Mar 2021 20:50:00 +0900
To: cygwin@cygwin.com
Subject: Re: segfault on 32bit cygwin snapshot
Message-Id: <20210304205000.4ac34afe1a8b767ea2986291@nifty.ne.jp>
In-Reply-To: <CAB8Xom-HwxH9LnbLL8cAoXh60tjU592T6XFEDJzvhv28Do-UsQ@mail.gmail.com>
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>
 <20210301212542.8b1749f92af62c01b008f25a@nifty.ne.jp>
 <20210302200308.62db4fe01f78fb35a538784f@nifty.ne.jp>
 <YD5eXbxBWbUUSwcM@calimero.vinschen.de>
 <20210303185621.b048287526901af6a4c8200a@nifty.ne.jp>
 <YD9sSea32T7GqlJr@calimero.vinschen.de>
 <20210304180534.7c3825e6ee989a2bf62f0652@nifty.ne.jp>
 <CAB8Xom-HwxH9LnbLL8cAoXh60tjU592T6XFEDJzvhv28Do-UsQ@mail.gmail.com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
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 <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin@cygwin.com>
Reply-To: Takashi Yano <takashi.yano@nifty.ne.jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On Thu, 4 Mar 2021 12:11:11 +0100
marco atzeri wrote:
> I have no problem to patch Python to solve the issue,
> but I have not seen evidence of the dlsym mechanism .
> But of course I an NOT and expert in this field.
> 
> If someone looking to the code can give me some hints,
> I will appreciate

I am also not sure where the dlsym() is used in python.
At least, os.uname() works in python 3.8.7 and 2.7.18 in my
environment even without that snippet. It seems that os.uname()
does not use dlsym(). Do I overlook something?

-- 
Takashi Yano <takashi.yano@nifty.ne.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
