segfault on 32bit cygwin snapshot

Marco Atzeri
Fri Mar 5 08:09:07 GMT 2021

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


More information about the Cygwin mailing list