From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: w6b7rk5yu4mt25v3 <w6b7rk5yu4mt25v3@protonmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Fw: Re: Fw: Re: Why do these mprotect always fail?
Date: Wed, 15 Feb 2023 17:33:19 +0100 [thread overview]
Message-ID: <Y+0JTyNpVqvpZvW0@calimero.vinschen.de> (raw)
In-Reply-To: <3HScWpQC8pjnPC4OBYIhgMMGaPTBCH_T8o8mMC72UMMMgtodqjjUCRpC81hW8SF9PUk-e3rmxeI8y45aaOGTrZ1MFu7FK3tJ-3XXclG2i3I=@protonmail.com>
On Feb 15 15:31, w6b7rk5yu4mt25v3 via Cygwin wrote:
> I asked the developer of the interpreter. He said it's OK to use the PAGE_SIZE value different than 4096. So I used this dirty hack:
>
> #ifndef __CYGWIN__
> #define PAGE_SIZE 4096
> #endif
>
> This means on Cygwin it will use the default PAGE_SIZE defined on limits.h (I'm taking advantage of the naming conflict here so I don't have to rename PAGE_SIZE to JIT_PAGE_SIZE as suggested by the developer of the interpreter).
>
> The result is it's no longer error with "Unable to mprotect" but will
> silently crashed without any error messages printed on the screen. So
> after all, it's Cygwin's quirks here.
I still think it's a bug in the code which requires some debugging effort
on your side.
Having said that, if it's actually a Cygwin bug and you want it fixed,
please provide a *simple*, self-contained testcase in plain C, with a
minimum of code to reproduce the issue, and which compiles OOTB.
Corinna
next prev parent reply other threads:[~2023-02-15 16:33 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 ` Fw: " w6b7rk5yu4mt25v3
2023-02-15 12:13 ` 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 [this message]
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=Y+0JTyNpVqvpZvW0@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=w6b7rk5yu4mt25v3@protonmail.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).