search for: asrl

Yes, we have no ASRL with -no_pie. Can we disable ASRL even with -pie? On linux we can do it with "setarch x86_64 -R". Another question: if asan would require -no_pie on Mac, will this be a serious limitation? Thanks, --kcc On Fri, Dec 9, 2011 at 11:07 AM, Eric Christopher <echristo at apple.com>wro...

On Fri, Dec 9, 2011 at 11:16 AM, Eric Christopher <echristo at apple.com>wrote: > > On Dec 9, 2011, at 11:12 AM, Kostya Serebryany wrote: > > > Yes, we have no ASRL with -no_pie. > > Can we disable ASRL even with -pie? > > On linux we can do it with "setarch x86_64 -R". > > > > You asked about link time. Now it sounds like you're talking about runtime? > Link time is of course better. But if there is a syscall (like th...

On Dec 9, 2011, at 11:23 AM, Kostya Serebryany wrote: > > > On Fri, Dec 9, 2011 at 11:16 AM, Eric Christopher <echristo at apple.com> wrote: > > On Dec 9, 2011, at 11:12 AM, Kostya Serebryany wrote: > > > Yes, we have no ASRL with -no_pie. > > Can we disable ASRL even with -pie? > > On linux we can do it with "setarch x86_64 -R". > > > > You asked about link time. Now it sounds like you're talking about runtime? > > Link time is of course better. > But if there is a sysc...

On Dec 9, 2011, at 11:12 AM, Kostya Serebryany wrote: > Yes, we have no ASRL with -no_pie. > Can we disable ASRL even with -pie? > On linux we can do it with "setarch x86_64 -R". > You asked about link time. Now it sounds like you're talking about runtime? > Another question: if asan would require -no_pie on Mac, will this be a serious limitat...

...om>wrote: > > On Dec 9, 2011, at 11:23 AM, Kostya Serebryany wrote: > > > > On Fri, Dec 9, 2011 at 11:16 AM, Eric Christopher <echristo at apple.com>wrote: > >> >> On Dec 9, 2011, at 11:12 AM, Kostya Serebryany wrote: >> >> > Yes, we have no ASRL with -no_pie. >> > Can we disable ASRL even with -pie? >> > On linux we can do it with "setarch x86_64 -R". >> > >> >> You asked about link time. Now it sounds like you're talking about >> runtime? >> > > Link time is of course...

...c by setting disable_aslr to 0. In this case we can print the big warning (if someone wants to run the binary under GDB, ASLR will anyway be disabled). > > I would prefer just to print a descriptive warning message and exit: >    ==123== ERROR: AddressSanitizer on MacOS requires to disable ASRL for the > executable. >    ==123== ERROR: You can do it this way: >    ==123== ERROR: <how to disable ASLR> >    ==123== ABORTING "pass the no_pie to your linker" We can do this in the Clang driver, but a proper fix will involve removing all the instances of -pie from th...

Options when creating a main executable -pie This makes a special kind of main executable that is position independent (PIE). On Mac OS X 10.5 and later, the OS the OS will load a PIE at a random address each time it is executed. You cannot create a PIE from .o files compiled with -mdy- namic-no-pic. That means the

+llvmdev Question to MacOS gurus: is there a way to disable ASLR (address space layout randomization) on Darwin at link time instead of doing setenv("DYLD_NO_PIE", "1", 1); and reexec? Thanks, --kcc On Fri, Dec 9, 2011 at 4:28 AM, Alexander Potapenko <glider at google.com>wrote: > The attached patch introduces the disable_aslr option (off by default) > and the

Hi All, We use an automatic home share of the form below. [homes] comment = User Home Dirs path = /home/%U valid users = %S read only = No create mask = 0777 directory mask = 0777 browseable = yes guest ok = no Is it possible to do group shares a similar way? We want to have an automatic group share for any secondary groups with a

...to 0. In this case > we can print the big warning (if someone wants to run the binary under > GDB, ASLR will anyway be disabled). > > > > I would prefer just to print a descriptive warning message and exit: > > ==123== ERROR: AddressSanitizer on MacOS requires to disable ASRL for > the > > executable. > > ==123== ERROR: You can do it this way: > > ==123== ERROR: <how to disable ASLR> > > ==123== ABORTING > "pass the no_pie to your linker" > We can do this in the Clang driver, but a proper fix will involve > re...