On 18 August 2014 17:43, <[email protected]> wrote:
> The logic behind the name is that it's not as though the debugger is able to
> turn aslr on on a system that doesn't have it - so "-aslr on/true/yes"
> doesn't make sense - but rather the debugger is running on a system with
> ASLR, in which case the question is whether the debugger should disable it or
> not for this launch. So --disable-aslr true/false is answering the question
> "should I disable aslr.
I suppose that's fair, and GDB does the same ("set
disable-randomization off"). Despite the double negative being
awkward I guess it's reasonable for ASLR.
_______________________________________________
lldb-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
