[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 12:28:29 -0400 (EDT) |
Update of bug #66089 (group libffcall):
Status: None => Need Info
Assigned to: None => haible
_______________________________________________________
Follow-up Comment #1:
Thanks for the report.
On which version of macOS do you see this?
When a SIGABRT occurs, what is the stack trace? (I know macOS makes it
impossible to use a debugger. But what stack trace do you get by using
libbacktrace https://github.com/ianlancetaylor/libbacktrace and the gnulib
module 'abort-debug'?)
> If you want I can ... make a pull request.
We don't work with pull requests here. Instead we work with patches, either
attached to a ticket like here, or sent to the mailing list.
_______________________________________________________
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