This is the mail archive of the cygwin-developers mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On May 13 10:36, Corinna Vinschen wrote:Maybe I've been confused by some of that contradictory info as well, but I had the impression that PE improves dll placement (still random, but at least consistent for a given login sesssion), but does nothing at all for heaps, thread stacks, or non-image file mappings. I'd love to be even partly wrong tho...So we now know that we are actually observing a part of the ASLR strategy of NT6. Heap addresses are always randomized. Yes, there is a PE flag which controls ASLR on a per-executable basis, but unfortunately this only influences the usage of ASLR for the executable image itself, as well as the thread stacks. There's no way at all to disable heap ASLR.It appears that I misread. The PE flag might not influence stack randomization, but what I found in the net is contradictory. However, even if stack ASLR is always on, it seems the preferred addresses of thread stacks are also in the range below 0x20000000.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |