X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org DFC353836CFA
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1676889227;
	bh=k7YHfMRvVSUkNfCIkn+pLJe33U7CPTxDFZjYL3p45yY=;
	h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=OacYRmpUW6Mk/Tb7c2BSMP7EuKZhD5YphEORId7cvlxyet95+tb2A68g+gFyst6Bq
	6+xu+TOuwIrGp2GOLdBUkzmSrFdDkETDdylRQRQeJqEedllksqnU3EkSNz+HU5DWtt
	7SjBYoEeyd8pY9VWsDDzfAm1l2MRxEsVS217JuUI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 1D740385B51E
Date:	Sun, 19 Feb 2023 16:56:15 +0000
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>,
	"cygwin-developers AT cygwin DOT com" <cygwin-developers AT cygwin DOT com>
Subject:	I discovered the problems why the program I'm trying to port crashed
Message-ID:	<bEc_juo0ZomxwHLHf1mKfbz_S9hMzlkUU691bG-cOPnyCDtaXjdjxwpMgZbbxq0ljP1LU4qJGYOr2IMwKRBmNzsU5bEqovMtZ37aqQOEUXY=@protonmail.com>
Feedback-ID:	67221101:user:proton
MIME-Version:	1.0
X-Spam-Status:	No, score=-1.0 required=5.0 tests=BAYES_00, DATE_IN_PAST_12_24,
	DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF,
	FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, SPF_HELO_PASS, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) 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-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:	w6b7rk5yu4mt25v3 via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	w6b7rk5yu4mt25v3 <w6b7rk5yu4mt25v3 AT protonmail DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Quoted from https://cygwin.com/pipermail/cygwin-cvs/2020q3/014516.html:

"The file mapping will be only a single page, 4K, and since 64 bit systems don't support the AT_ROUND_TO_PAGE flag, the remainder of the 64K slot will result in a SEGV when accessed."

"The justification is that there's very likely no application actually utilizing the map beyond EOF, and we know that all bytes beyond EOF are set to 0 anyway."

Unfortunately, the application I'm trying to port do exactly that. If you set JIT_PAGE_SIZE to 64k (same as PAGE_SIZE) to satisfy mprotect then it will expect the whole 64k to be accessible. On other systems, no problems. On Cygwin, crashed with segmentation fault. I was right. Not the application's bug, but Cygwin's quirk (I called it as a quirk but not a bug, because it's a limitation of the platform).

Goodbye. It's better to use WSL directly than messing with Cygwin nowadays.

Sent with Proton Mail secure email.

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