https://bugs.winehq.org/show_bug.cgi?id=54420
--- Comment #1 from Brendan Shanks bshanks@codeweavers.com --- Yep, dyld (at least on Ventura, didn't test Monterey) allocates private memory in that region very early, before any part of the preloader runs.
A zero-fill section does succeed in reserving this memory, but the dyld allocations start right after, so picking the size would be tricky. Once wow64 is working upstream there will likely be other memory reservation changes needed, we can revisit this then.
(We know of an EXE with an image base of 0x10000 that fails to run on Ventura, but does work when a zerofill is used to reserve it, so that's promising).
==== regions for process 61077 (non-writable and writable regions are interleaved) REGION TYPE START - END [ VSIZE RSDNT DIRTY SWAP] PRT/MAX SHRMOD PURGE REGION DETAIL dyld private memory 1000-41000 [ 256K 48K 48K 0K] rw-/rwx SM=PRV dyld private memory 41000-81000 [ 256K 16K 16K 0K] rw-/rwx SM=PRV