Fixed here:
https://gitlab.com/qemu-project/qemu/-/commit/c118881ee607dcac
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914849
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914849
Title:
mprotect fails after MacOS 11.2 on arm mac
Status in QEMU:
Fix
It works for me when I use "./configure --enable-debug-tcg --extra-
cflags=-I/opt/homebrew/include".
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914849
Title:
mprotect fails after MacOS 11.2 on
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914849
Title:
mprotect fails after MacOS 11.2 on arm mac
Status in QEMU:
Confirmed
Bug
...@chaenomeles.canonical.com
Subject: [Bug 1914849] Re: mprotect fails after MacOS 11.2 on arm mac
=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scri
The patch can be used as a workaround for now:
diff --git a/util/osdep.c b/util/osdep.c
index 66d01b9160..76be8c295b 100644
--- a/util/osdep.c
+++ b/util/osdep.c
@@ -110,6 +110,9 @@ int qemu_mprotect_none(void *addr, size_t size)
{
#ifdef _WIN32
return qemu_mprotect__osdep(addr, size,
I hit the same problem and did some initial investigation with
Toshifumi.
Here is a more exhaustive test program I wrote based on the post on the
Apple Developer Forums and the result shows that very interesting
behavior of mmap and mprotect since macOS 11.2.
Thanks for submitting the ticket.
I've just stumbled upon it after updating to 11.2.
The question was already asked on apple developer forums:
https://developer.apple.com/forums/thread/672804
And there's a thread going on with regard to broken nodejs on 11.2:
