X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 84FD4383FDFF DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1676888308; bh=m7gaxs1EpnCWRo0RooRaWPG/tOOOOcfbwVLPNldgorU=; 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=Mdh18EDN7p+BaKs0muhOgsX4QVevImQ2tN3QqOngkTQH0YEz5eCgxwbh3nPO+LEhZ zREI9N5vPFDyQsdZSn1HQJ0mG5kdgTk+dyaibnSMaYgln9Ifcpqwk7aL6B+ojgS+Qu NLPUPGZEuWWpmT+ryCRDw7OIKIOWNLUQC6oRqhmU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 18F2D380E0CE Date: Sun, 19 Feb 2023 13:08:30 +0000 To: cygwin AT cygwin DOT com Subject: Re: Fw: Re: Fw: Re: Why do these mprotect always fail? Message-ID: <2sLxaK-alDruU1hBajs4HCL82MYIxVHQqam2ogOcvGixLJ8yhI1avBVKiKANKAL-nLPBqLdkttsufxIpZ9cupOz3tPgT8heQSbIp0XmVT4s=@protonmail.com> In-Reply-To: References: <0Qjpbo0t_1WTd9--kVw5gLR1PdJzG7myKYzhxdzDIqnWYwLnywFCtSbekykskWViaSJM_bcLQBEFT_wg4-IApgEYrX5bHFIZH7Ro40oDYGs=@protonmail.com> <3HScWpQC8pjnPC4OBYIhgMMGaPTBCH_T8o8mMC72UMMMgtodqjjUCRpC81hW8SF9PUk-e3rmxeI8y45aaOGTrZ1MFu7FK3tJ-3XXclG2i3I=@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 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: w6b7rk5yu4mt25v3 via Cygwin Reply-To: w6b7rk5yu4mt25v3 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" See strace: 544091 601347 [main] obr 1831 mprotect: mprotect (addr: 0xA00100000, len 65536, prot 0x7) 59 601406 [main] obr 1831 mprotect: 0 = mprotect () 166 601572 [main] obr 1831 mmap: addr 0x0, len 327680, prot 0x3, flags 0x22, fd -1, off 0x0 123 601695 [main] obr 1831 mmap: 0x6FFFFFFB0000 = mmap() 95 601790 [main] obr 1831 mprotect: mprotect (addr: 0x6FFFFFFC0000, len 196608, prot 0x7) 88 601878 [main] obr 1831 mprotect: 0 = mprotect () 255 602133 [main] obr 1831 mmap: addr 0x0, len 393216, prot 0x3, flags 0x22, fd -1, off 0x0 102 602235 [main] obr 1831 mmap: 0x6FFFFFF50000 = mmap() 108 602343 [main] obr 1831 mprotect: mprotect (addr: 0x6FFFFFF60000, len 262144, prot 0x7) 47 602390 [main] obr 1831 mprotect: 0 = mprotect () 245 602635 [main] obr 1831 mmap: addr 0x0, len 458752, prot 0x3, flags 0x22, fd -1, off 0x0 44 602679 [main] obr 1831 mmap: 0x6FFFFFEE0000 = mmap() 46 602725 [main] obr 1831 mprotect: mprotect (addr: 0x6FFFFFEF0000, len 327680, prot 0x7) 39 602764 [main] obr 1831 mprotect: 0 = mprotect () --- Process 3796 (pid: 1831), exception c0000005 at 0000000a00100061 --- Process 3796 (pid: 1831) thread 2928 exited with status 0xc0000005 --- Process 3796 (pid: 1831) exited with status 0xc0000005 Segmentation fault I still think it's Cygwin's bug. Sent with Proton Mail secure email. ------- Original Message ------- On Wednesday, February 15th, 2023 at 23:33, Corinna Vinschen wrote: > 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 -- 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