From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-01.nifty.com (conssluserg-01.nifty.com [210.131.2.80]) by sourceware.org (Postfix) with ESMTPS id 0FAA63840C0C for ; Thu, 4 Mar 2021 11:50:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0FAA63840C0C Received: from Express5800-S70 (y085178.dynamic.ppp.asahi-net.or.jp [118.243.85.178]) (authenticated) by conssluserg-01.nifty.com with ESMTP id 124Bnxav028161 for ; Thu, 4 Mar 2021 20:50:00 +0900 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 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: segfault on 32bit cygwin snapshot Message-Id: <20210304205000.4ac34afe1a8b767ea2986291@nifty.ne.jp> In-Reply-To: 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> <20210303185621.b048287526901af6a4c8200a@nifty.ne.jp> <20210304180534.7c3825e6ee989a2bf62f0652@nifty.ne.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2021 11:50:29 -0000 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