X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org D13903834408
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1614961835;
	bh=h2al33Y7K6fDO00YjC9j99dLh6YZujdw6FN3hTm3i/I=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=hM3nM+8CaqXNBhtTuCmFbKiUusyW/oaAqAS4QZpbmsoW3NCjc9Q3Itd23+wdC3Joe
	+cP8GMccPdkkBe7f5DKzwkmqsabNdJLxYq0GJAkapiX/xLFS4XqXpILkGJt9IFVsVa
	M4cZxDYVkjhpJm4+5MQiGrMjUdNJH76Q3SLUjZHs=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 5118F3840C0E
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language
	:content-transfer-encoding;
	bh=0rLuYLoCx7WYwD9OuJh+2pvRo1nZ3GLgEfT0u0jPzTg=;
	b=Gd96POZHxC1+HSlvkKLH0WlrByv34lka+5ohTZ65YZpZdFHnOr+wAQ51TX19Bs4jII
	u2Gbq0dCriqkxvwJPh503eGJGqgL/dRCQFPCSCbhsMQPUhqR2A/6t8Jw0drXnOOOW2VQ
	HzSdsL20u8a/eC59YCDqSbPJXYfJ7XEIvPnMmblanDDduHXe96Yv7I/9RQ7jwLnDCR6r
	iZAK5dgGseodUv7ecjssaygjBmcsk2yHQnOP+QSXw0ePGUh1jDG6zwZPORj0WKADYP79
	RyIhiZnZPHMK4jViD00OQSmwpoeybQTZ2iNmQ3DbBxE48mStJdpNdkDM0a2QgqKF2MZT
	DZKA==
X-Gm-Message-State:	AOAM531qAUzM5p/LYROT591ABQJOAnVd9r4ayDbgS/M5J74xXIeQtHV7
	n8YZV1qfPENyVZaubVrxWmfG94g/dza1Xw==
X-Google-Smtp-Source:	ABdhPJzyrc6NRhanohHC0fk8mWzuCZCTHvccD3SvzOvKqhaYsj4EOCJiMF2WQyt5QaBqz8KrQqVn8Q==
X-Received:	by 2002:a05:6402:1c1b:: with SMTP id
	ck27mr9825561edb.223.1614961832347;
	Fri, 05 Mar 2021 08:30:32 -0800 (PST)
Subject:	Re: segfault on 32bit cygwin snapshot
To:	cygwin AT cygwin DOT com
References:	<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>
	<CAB8Xom-HwxH9LnbLL8cAoXh60tjU592T6XFEDJzvhv28Do-UsQ AT mail DOT gmail DOT com>
	<20210304205000 DOT 4ac34afe1a8b767ea2986291 AT nifty DOT ne DOT jp>
	<b7338aaa-c1e1-1816-35f8-666c2f6ac618 AT cornell DOT edu>
	<98df59b3-a139-03d2-c8c5-31ff4f8448ab AT gmail DOT com>
	<625cb9d2-b6cc-3ada-eea9-44a5e73da17c AT gmail DOT com>
	<72a86908-e150-2070-24f7-79ca82de9916 AT maxrnd DOT com>
	<YEJDaQQ+U/+j3uQb AT calimero DOT vinschen DOT de>
Message-ID:	<df03a23e-10fd-b3e1-b8cf-e1a927a569fc@gmail.com>
Date:	Fri, 5 Mar 2021 17:30:30 +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:	<YEJDaQQ+U/+j3uQb@calimero.vinschen.de>
X-Spam-Status:	No, score=-0.1 required=5.0 tests=BAYES_00, BODY_8BITS,
	DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM,
	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 AT cygwin DOT com
X-Mailman-Version:	2.1.29
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:	Marco Atzeri via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 125GUcEL017437

On 05.03.2021 15:42, Corinna Vinschen via Cygwin wrote:
> On Mar  5 01:11, Mark Geisert wrote:
>> Marco Atzeri via Cygwin wrote:
>>> 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
>>
>> I had concerns that I had somehow corrupted my build environment, and it was
>> Marco's successes that convinced me to reinstall 3.1.7 to recover a
>> known-good environment.  Then seeing Marco go ahead and release the
>> different Python releases (yay!) I didn't investigate any further.
>>
>> I'm now trying to locate the os.uname usage of dlopen/dlsym again just for
>> the record but am having some difficulty.  I'll reply again when I've got
>> it.
> 
> Guys,
> 
> if it turns out that we fixed a problem that doesn't actually is a
> real-world problem, I'm wondering if we shouldn't just revert the Cygwin
> patch we're talking about here (commit 532b91d24e9496) and be done with
> it.
> 
> Special casing dynamic loading of uname just to support some experimental
> bordercase doesn't make much sense.  In that case I'm all for "don't do
> that"!
> 
> 
> Corinna


Python has a lot of problem but not this one for what I can see

$ python3.8 /usr/lib/python3.8/test/pythoninfo.py  | grep uname
os.uname: posix.uname_result(sysname='CYGWIN_NT-10.0-19041-WOW64', 
nodename='LAPTOP-82F08ILC', release='3.1.7-340.i686', 
version='2020-08-22 19:03 UTC', machine='i686')

and similar for the other version






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

- Raw text -