[ld] 2.36 PE flags changes (PR19011, commit 514b4e19)

[ASSI]

Jan Beulich via Binutils writes:
> ... 0x1400000 doesn't look like a randomized (image base?) address,
> but a link-time one. So I wonder what specific "flags" changes you
> are talking about.

That's the stack and it has to be at a fixed address.  Setting the ASLR
flag on the executable has either caused something else to be mapped
there during the fork emulation or the stack to get moved.  Either way
it's not going to work since the map in the child process has to be
exactly the same as the one in the parent.

> Irrespective I do agree with what I imply from your posting - the
> change, despite its good intentions, didn't care enough about
> compatibility with existing use cases.

It almost never hurts to have an option of switching back to the old
behaviour and then see who needs to do it and why.

Just to make it clear, I'd love to have ASLR working for Cygwin, but the
behaviour of it on Windows doesn't allow that currently.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds