Well, more like what I mean is that I would just log a warning that says "Option not supported on this platform". I wouldn't make it crash.
On Fri, Aug 15, 2014 at 10:05 AM, <jing...@apple.com> wrote: > Note, while I appreciate the elegance of not having options that don't > make sense for a particular platform note that it will mean that if I'm > used to working on say Linux, and I put: > > command alias run process launch -A -- > > in my .lldbinit, then move over to windows and carry my .lldbinit with me, > my run command will no longer work. So there's a trade-off between > cleanliness and portability here... > > Jim > > > > > On Aug 15, 2014, at 9:27 AM, Zachary Turner <ztur...@google.com> wrote: > > > > FWIW, once I get debugging working on Windows, I'm going to disable this > setting entirely as it doesn't make sense on Windows. Is ASLR per-launch / > per-process on other platforms? At least on Windows it's per-boot, so if > ASLR is enabled for a particular process, everything will be the same until > you reboot. > > > > > > On Fri, Aug 15, 2014 at 6:52 AM, Todd Fiala <tfi...@google.com> wrote: > > Thanks all. > > > > I'm going to start looking into this today. > > > > > > On Fri, Aug 15, 2014 at 1:00 AM, Colin Riley <co...@codeplay.com> wrote: > > I'd agree with the default behavior being off and the command being > changed to an enable style. All targets we have worked with certainly > default to off, or don't have the feature at all. > > > > Colin > > > > > > > > On 15/08/2014 01:45, Eric Christopher wrote: > >> I believe that disabling by default would match the gdb behavior yes? > If nothing else, yes, I'm a fan of this :) > >> > >> -eric > >> On Thu Aug 14 2014 at 5:30:52 PM Todd Fiala <tfi...@google.com> wrote: > >> Hey all, > >> > >> Regarding this bug: > >> http://llvm.org/bugs/show_bug.cgi?id=20658 > >> > >> We've been discussing the idea of having ASLR disabled by default when > launching processes within lldb. Currently it looks like the default > behavior is to have it enabled, and require explicitly disabling to get > that behavior for the process. > >> > >> It seems like it might make more sense to have it disabled by default - > that way code references would likely be static across debugger runs, which > seems to be more what we want when tracking down issues across code runs. > >> > >> Any thoughts on this? > >> > >> The counterargument I could make for changing it would be (aside from > legacy compatibility issues perhaps on the MacOSX/iOS side) - taking the > exe out of its native state on the OS. If a bug is ASLR sensitive, the > user might miss it. And so behavior in the debugger could differ from the > exe in its native state. Not sure how relevant that is for the majority of > usages, though. > >> > >> I'll be fixing the fact that Linux is ignoring this altogether. But > while I'm in there, I could flip the default if we wanted to do it. If not > globally, we'd probably pursue defaulting it on Linux (and Ed seems to like > it for FreeBSD as well, so maybe for not Apple in that case?) > >> -- > >> Todd Fiala | Software Engineer | tfi...@google.com | > 650-943-3180 > >> _______________________________________________ > >> lldb-dev mailing list > >> lldb-dev@cs.uiuc.edu > >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > >> > >> > >> _______________________________________________ > >> lldb-dev mailing list > >> > >> lldb-dev@cs.uiuc.edu > >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > > > > -- > > - Colin Riley > > Games Technology Director > > > > Codeplay Software Ltd > > 45 York Place, Edinburgh, EH1 3HP > > Tel: 0131 466 0503 > > Fax: 0131 557 6600 > > Website: > > http://www.codeplay.com > > > > Twitter: > > https://twitter.com/codeplaysoft > > > > > > This email and any attachments may contain confidential and /or > privileged information and is for use by the addressee only. If you are not > the intended recipient, please notify Codeplay Software Ltd immediately and > delete the message from your computer. You may not copy or forward it,or > use or disclose its contents to any other person. Any views or other > information in this message which do not relate to our business are not > authorized by Codeplay software Ltd, nor does this message form part of any > contract unless so stated. > > As internet communications are capable of data corruption Codeplay > Software Ltd does not accept any responsibility for any changes made to > this message after it was sent. Please note that Codeplay Software Ltd does > not accept any liability or responsibility for viruses and it is your > responsibility to scan any attachments. > > Company registered in England and Wales, number: 04567874 > > Registered office: 81 Linkfield Street, Redhill RH1 6BY > > > > > > _______________________________________________ > > lldb-dev mailing list > > lldb-dev@cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > > > > > > > > > > -- > > Todd Fiala | Software Engineer | tfi...@google.com | > 650-943-3180 > > > > > > _______________________________________________ > > lldb-dev mailing list > > lldb-dev@cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > > > > > > _______________________________________________ > > lldb-dev mailing list > > lldb-dev@cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > >
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
