[lldb-dev] ASLR disabled by default - thoughts?

Chandler Carruth chandlerc at google.com
Fri Aug 15 10:18:04 PDT 2014

On Fri, Aug 15, 2014 at 10:03 AM, Zachary Turner <zturner at google.com> wrote:

> Correct, AFAIK the only way to disable ASLR in Windows is:
> a) Editing a registry setting which will require a reboot and be
> system-wide
> b) Compiling your executable with a specific flag which has been set to
> enable ASLR by default since VS 2012.
> c) Using the EMET utility <http://support.microsoft.com/kb/2458544>
> (untested, but I guess should work).  Regardless, it's a manual step and
> would require elevation (aka sudo)
> Maybe it's just because I'm used to an environment where ASLR is per-boot,
> but what are the issues with debugging when ASLR is enabled?  Source/line
> breakpoints can just be resolved every time you debug.  Same with symbol
> breakpoints.  Even absolute address breakpoints can be translated to
> Module+offset and persist across ASLR.  The only things I can think of off
> the top of my head are hardware data breakpoints, and printing addresses to
> log files.  Is there other stuff that is complicated by ASLR?

Watchpoints on heap-allocated memory (whether software or hardware).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140815/0d05a5bd/attachment.html>

More information about the lldb-dev mailing list