[lldb-dev] Add --enable-aslr flag

Chandler Carruth chandlerc at google.com
Sat Aug 16 19:39:20 PDT 2014

On Sat, Aug 16, 2014 at 7:31 PM, Todd Fiala <tfiala at google.com> wrote:

> I'm not sure it really makes sense in this case to try to implement
> --enable-aslr on the process launch command now that I get the flow of the
> target settings, unless we change the model to do something like this:
> 1. If the process launch command explicitly sets --enable-aslr or
> --disable-aslr, do *that*.
> 2. Otherwise, if the target.disable-aslr setting is true, disable ASLR.
> 3. Otherwise, we get the default ASLR behavior for the system.
> Does that sound reasonable?  I think it makes intuitive sense.  In that
> case, the options setting in the process launch command becomes a tri-state
> and only if it's unresolved do we go to the target setting.
> Thoughts?

Sounds good, but we should also *error* if an attempt to launch a process
is made with either setting when that setting is unsupported on the system.
Or at least a stringent warning.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140816/b19bcebe/attachment.html>

More information about the lldb-dev mailing list