[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the
|
From: |
Bruno Haible |
|
Subject: |
[bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the same time |
|
Date: |
Wed, 14 Aug 2024 13:08:35 -0400 (EDT) |
Follow-up Comment #2, bug #66089 (group libffcall):
Also:
Which version of libffcall are you using?
What exactly is the scenario (test program) that causes the SIGABRT on macOS?
I'm asking because my continuous integration of libffcall shows no problems on
macOS versions 12, 13, 14: https://github.com/gnu-libffcall/ci-check/actions
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66089>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the same time, Lorenzo Daneo, 2024/08/14
- [bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the same time, Bruno Haible, 2024/08/14
- [bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the same time, Bruno Haible, 2024/08/14
- [bug #66089] On macos mprotect can't be PROT_WRITE and PROT_EXEC at the same time, Bruno Haible, 2024/08/15
- [bug #66089] On macos 14, mmap with PROT_READ | PROT_EXEC fails, Bruno Haible, 2024/08/17
- [bug #66089] On macos 14, mmap with PROT_READ | PROT_EXEC fails, Bruno Haible, 2024/08/17