DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5576F3851C39
Subject: Re: segfault on 32bit cygwin snapshot
To: cygwin@cygwin.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>
 <20210304205000.4ac34afe1a8b767ea2986291@nifty.ne.jp>
 <b7338aaa-c1e1-1816-35f8-666c2f6ac618@cornell.edu>
 <98df59b3-a139-03d2-c8c5-31ff4f8448ab@gmail.com>
Message-ID: <625cb9d2-b6cc-3ada-eea9-44a5e73da17c@gmail.com>
Date: Fri, 5 Mar 2021 09:09:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <98df59b3-a139-03d2-c8c5-31ff4f8448ab@gmail.com>
Content-Language: it
Precedence: list
From: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Reply-To: Marco Atzeri <marco.atzeri@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

On 04.03.2021 21:17, Marco Atzeri wrote:
> On 04.03.2021 16:17, Ken Brown via Cygwin wrote:
>> On 3/4/2021 6:50 AM, Takashi Yano via Cygwin wrote:
>>> 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?
>>
>> This all started because Mark reported a problem building python 3.8.3:
>>
>>    https://cygwin.com/pipermail/cygwin-apps/2020-December/040765.html
>>    
>> https://cygwin.com/pipermail/cygwin-developers/2020-December/012019.html
>>
>> It's strange that Marco never bumped into the problem.
>>
>> Ken
> 
> I never built python using cygwin snapshots as Mark was trying to do,
> all my builds were using 3.1.7.
> 
> Let me set a separate enviroment for building on latest snapshot

I can not replicate with latest snapshot

$ uname -svr
CYGWIN_NT-10.0-WOW 3.2.0s(0.340/5/3) 2021-03-01 15:42

nor in 64bit when building 3.8.8

For what I see the DLL is always using a proper import
from cygwin1.dll

$ objdump -x libpython3.8.dll |grep uname
         2b9de0   2170  uname
         2b9de8   2171  uname_x

the only thing not standard on my build system is a case sensitive
filesystem and mount


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