https://bugs.winehq.org/show_bug.cgi?id=54420
--- Comment #2 from Gcenx gcenx83@gmail.com --- (In reply to Brendan Shanks from comment #1)
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.
So there it could still be worked around it’s just going to be a PITA
Unless something changed in a later macOS Monterey security patch preloader didn’t complain this started the moment I’d upgraded to Ventura.
Once wow64 is working upstream there will likely be other memory reservation changes needed, we can revisit this then.
Yep it’s rather unfortunate that WoW64 isn’t working at all currently not even generating a full wineprefix this will endup causing more bug reports since it’s enabled by default, I’d already created one https://bugs.winehq.org/show_bug.cgi?id=54367
(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).
Could you disclose what exe is affected by this?