From: w6b7rk5yu4mt25v3 <w6b7rk5yu4mt25v3@protonmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Fw: Re: Why do these mprotect always fail?
Date: Wed, 15 Feb 2023 11:14:53 +0000 [thread overview]
Message-ID: <TlepM9ESIu1ZpPCpz1vzmSoBKsKnuUABID2BREun8gb9tEPApKByf5s-_DHR9C6h48OdPFnU5uZ0Xc4JTTd-gtPH2RqhOHgOiSh-spI9K88=@protonmail.com> (raw)
In-Reply-To: <Y+y0zRQWVRWBkhCX@calimero.vinschen.de>
PAGE_SIZE is just a naming conflict. If you change it to something else, JIT_PAGE_SIZE for example, it still fails. The problem is Cygwin is not fine with the particular value 4096 but the program needs the value to be exactly 4096. About why I also sent to developer list, see:
https://cygwin.com/pipermail/cygwin-developers/2020-July/011913.html
https://cygwin.com/pipermail/cygwin/2002-January/068158.html
This problem is well known at least.
Sent with Proton Mail secure email.
------- Forwarded Message -------
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
Date: On Wednesday, February 15th, 2023 at 17:32
Subject: Re: Why do these mprotect always fail?
To: cygwin@cygwin.com <cygwin@cygwin.com>
CC: w6b7rk5yu4mt25v3 <w6b7rk5yu4mt25v3@protonmail.com>
> 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.
>
>
> Corinna
>
>
> () https://cygwin.com/acronyms/#STC
next prev parent reply other threads:[~2023-02-15 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:38 w6b7rk5yu4mt25v3
2023-02-15 9:43 ` w6b7rk5yu4mt25v3
2023-02-15 10:32 ` Corinna Vinschen
2023-02-15 11:14 ` w6b7rk5yu4mt25v3 [this message]
2023-02-15 12:13 ` Fw: " Corinna Vinschen
2023-02-15 12:40 ` w6b7rk5yu4mt25v3
2023-02-15 13:02 ` Oskar Skog
2023-02-15 15:31 ` Fw: " w6b7rk5yu4mt25v3
2023-02-15 16:33 ` Corinna Vinschen
2023-02-15 17:20 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-02-19 13:08 ` w6b7rk5yu4mt25v3
2023-02-19 15:40 ` Fw: " w6b7rk5yu4mt25v3
2023-02-15 13:41 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='TlepM9ESIu1ZpPCpz1vzmSoBKsKnuUABID2BREun8gb9tEPApKByf5s-_DHR9C6h48OdPFnU5uZ0Xc4JTTd-gtPH2RqhOHgOiSh-spI9K88=@protonmail.com' \
--to=w6b7rk5yu4mt25v3@protonmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).