On 2/10/21 2:55 AM, Roman Bolshakov wrote:
There's a change in mprotect() behaviour [1] in the latest macOS on M1
and it's not yet clear if it's going to be fixed by Apple. For now we
can avoid unsupported mprotect() calls. QEMU and qtests work fine
without it.

1.https://gist.github.com/hikalium/75ae822466ee4da13cbbe486498a191f

This is an unfortunate OS bug.

But I can use this as an opportunity to tidy up some memory management, and in the process go from NONE -> {RX,RW} instead.


r~

Reply via email to