https://bugs.winehq.org/show_bug.cgi?id=37585
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello Erich,
--- quote --- Is there some reason wine64 isn't mapped at this address to start with? It seems like it should be mapped so that it doesn't interfere with ntdll... --- quote ---
well, that's something to ask Alexandre about.
That part of the fixed address space layout hasn't been changed/touched for a while. The area where both core dlls ought to be mapped is one of the few fixed ranges, hence putting the wine ELF binary there too to avoid collisions with other (later) reserved areas and potentially avoid address space fragmentation might be a natural choice. Maybe I'm wrong and there is a different technical constraint why the interpreter section address is exactly there.
At introduction time of the fixed (prelink) addresses the target was clearly 32-bits (to cope with those brain damaged copy protection schemes). No one thought about 64-bit having similar problem - until now ;-)
Regards