X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 39C8C3858439
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1676464905;
	bh=bU3W+xbMakXpCJwTvZ3pMYpCtk09FVnaaAah/yFqsQw=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=Qp2+1HVcJPeuMGlm/Kk+22j2fcC1uEkMtKfktu5tZ4yuIY81dmXnCYWC3ryeIH0JF
	9PXnHrkN+N1UUPqK1AKRwnriCwmlcYIANs5JPza2vKSmhitBcAjwuKjkZlzsLdmKpF
	nz0VggtPF5APxuuv7ExWcWzlDZ7jJwF8INkpr5qY=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 40C273858D33
Date:	Wed, 15 Feb 2023 12:40:50 +0000
To:	cygwin AT cygwin DOT com
Subject:	Re: Fw: Re: Why do these mprotect always fail?
Message-ID:	<0Qjpbo0t_1WTd9--kVw5gLR1PdJzG7myKYzhxdzDIqnWYwLnywFCtSbekykskWViaSJM_bcLQBEFT_wg4-IApgEYrX5bHFIZH7Ro40oDYGs=@protonmail.com>
In-Reply-To:	<Y+zMcAP/eIZ1DTi8@calimero.vinschen.de>
References:	<yxifinJpR7DQ4XDFwpYMrUknNpsg8wu5T1KYPeNIwjf3FL_lYou0whmzg-XCoFgYlcz96k0yEjkrxCOQOOTztnk_tvW7ZNi8_riHbsOn-ZU=@protonmail.com>
	<ruVqVpKyYTyh3m-4mzaAg2pyhJAqlamcbUYKB8ghh_LwAKIqpabv0LNqlt8_Owfzx0Hc6c1C6nJE4Czf4hod2ukAWe3b6p_WAaaGLPk7CI8=@protonmail.com>
	<Y+y0zRQWVRWBkhCX AT calimero DOT vinschen DOT de>
	<TlepM9ESIu1ZpPCpz1vzmSoBKsKnuUABID2BREun8gb9tEPApKByf5s-_DHR9C6h48OdPFnU5uZ0Xc4JTTd-gtPH2RqhOHgOiSh-spI9K88=@protonmail.com>
	<Y+zMcAP/eIZ1DTi8 AT calimero DOT vinschen DOT de>
Feedback-ID:	67221101:user:proton
MIME-Version:	1.0
X-Spam-Status:	No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
	FREEMAIL_FROM, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS,
	TXREP autolearn=ham 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-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:	w6b7rk5yu4mt25v3 via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	w6b7rk5yu4mt25v3 <w6b7rk5yu4mt25v3 AT protonmail DOT com>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

You misunderstood what I said.

It's really just a naming conflict and a coincident. On the context of the source code (it's an interpreter), PAGE_SIZE is indeed JIT_PAGE_SIZE (not the system page size, but the page size defined internally by the interpreter). On Linux, the name doesn't conflict. On Cygwin, I found on limits.h and cygwin/limits.h already defined PAGE_SIZE so it caused a naming conflict:

#define __PAGESIZE 65536
#define PAGESIZE __PAGESIZE
#define PAGE_SIZE PAGESIZE

But the problem not related to the naming conflict. If I renamed PAGE_SIZE to JIT_PAGE_SIZE, the problem is still there. The problem is Cygwin will not work with JIT_PAGE_SIZE = 4096. Please have a look at the code I posted. It will always error with "Unable to mprotect".

Sent with Proton Mail secure email.

------- Original Message -------
On Wednesday, February 15th, 2023 at 19:13, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:


> On Feb 15 11:14, w6b7rk5yu4mt25v3 via Cygwin wrote:
> 
> > Corinna Vinschen wrote:
> > 
> > > cygwin-developers is for developers woking on Cygwin itself, not for
> > > developers using Cygwin to develop something else. I dropped the ML
> > > from the recipient list.
> > > 
> > > And please don't top-post. Thanks.
> > > 
> > > On Feb 15 09:43, w6b7rk5yu4mt25v3 via Cygwin wrote:
> > > 
> > > > Almost forgot, PAGE_SIZE is set to 4096. This is a Linux application,
> > > > when I compile on Cygwin it complained that PAGE_SIZE is redefined but
> > > > the compilation was success nevertheless. Only when I run the
> > > > application, I always exited with "Unable to mprotect".
> > > 
> > > PAGESIZE is 64K on Cygwin. If you change that, it breaks and you can
> > > keep the pieces.
> > > 
> > > It would be nice to send a complete, self-contained STC() in plain C,
> > > so reproducing your issue is simple and doesn't require to rework
> > > your code to get a running, debuggable testcase.
> > 
> > PAGE_SIZE is just a naming conflict. If you change it to something
> > else, JIT_PAGE_SIZE for example, it still fails.
> 
> 
> You're misunderstanding what PAGESIZE or PAGE_SIZE means. It's the
> system page size used for mappings, and it's a fixed value defined by
> the system and provided to you by the system headers and, especially,
> sysconf(_SC_PAGE_SIZE).
> 
> It's NOT something you can just change and think the result will still
> work. Especially given that mmap doesn't know that you changed a macro
> in your application code...
> 
> > The problem is Cygwin
> > is not fine with the particular value 4096 but the program needs the
> > value to be exactly 4096.
> 
> 
> Sorry, but that can't work. If the program actually demands it, it's
> non-portable.
> 
> 
> Corinna

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