On Sat, Aug 16, 2014 at 7:31 PM, Todd Fiala 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 laun
Ok so my mental model of how the default of the disable-aslr occurred was
flawed.
The way things currently work, the disable aslr internal flag is set if
either (1) the lldb target settings have disable-aslr set to true, or (2)
if --disable-aslr is given to the `process launch` command.
So when I
On Sat, Aug 16, 2014 at 4:33 PM, Todd Fiala wrote:
> Hey all,
>
> I've got Linux disabling ASLR per default as of a commit in review. I'm
> going to follow up with adding an --enable-aslr flag.
>
> Do we want to consider removing the --disable-aslr flag since disabling is
> the default, and it i
Hey all,
I've got Linux disabling ASLR per default as of a commit in review. I'm
going to follow up with adding an --enable-aslr flag.
Do we want to consider removing the --disable-aslr flag since disabling is
the default, and it is (perhaps) confusing to have the flag when it
currently doesn't
