Displaying 9 results from an estimated 9 matches for "mh_pie".
Did you mean:
magpie
2011 Dec 09
2
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...ASLR but keeps PIE on Snow Leopard or Lion.
> At the moment we're using DYLD_NO_PIE with Chromium binaries to
> disable ASLR at runtime.
One bit that may make sense is to support the newest (Lion) style and give
a descriptive error message for the other two cases? I.e. if we notice that
MH_PIE is set in the executable, but we're not on Lion and we don't have
DYLD_NO_PIE set in the environment give an error?
Or some combination of this.
-eric
2011 Dec 09
2
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...and the corresponding AsanDisableAslr function that should disable the
> address space randomization.
> This is now implemented for Mac OS 10.6 only.
> In order to do this we add DYLD_NO_PIE=1 to the env and restart the
> program.
>
> Next steps to be done are:
> -- check for MH_PIE bit -- if it is 0, we don't need to disable anything;
> -- use posix_spawnattr_setflags() to set the _POSIX_SPAWN_DISABLE_ASLR on
> 10.7
> -- disable ASLR on Linux, if needed.
>
> --
> Alexander Potapenko
> Software Engineer
> Google Moscow
>
-------------- next par...
2011 Dec 09
0
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...nd is Snow Leopard, where ASLR is controlled by the
DYLD_NO_PIE env var, which is read by the dynamic loader.
The third is Lion, which does not support DYLD_NO_PIE, but instead
supports a flag I've mentioned above. I suppose further Mac OS
releases will support only this way.
There also is the MH_PIE bit in the Mach-O header, which we can flip
to disable ASLR. But I'm not sure whether it won't disable the PIE
behavior at all.
Also, we'll need some special tool for that.
> 2. doing setenv+reexec. This will be a debugging nightmare for us and for
> users.
One can avoid setenv...
2011 Dec 09
0
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...> and the corresponding AsanDisableAslr function that should disable the
> address space randomization.
> This is now implemented for Mac OS 10.6 only.
> In order to do this we add DYLD_NO_PIE=1 to the env and restart the program.
>
> Next steps to be done are:
> -- check for MH_PIE bit -- if it is 0, we don't need to disable anything;
> -- use posix_spawnattr_setflags() to set the _POSIX_SPAWN_DISABLE_ASLR on 10.7
> -- disable ASLR on Linux, if needed.
>
> --
> Alexander Potapenko
> Software Engineer
> Google Moscow
>
> _____________________...
2011 Dec 09
2
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
On Fri, Dec 9, 2011 at 11:24 AM, Eric Christopher <echristo at apple.com>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.
>>
2011 Dec 09
0
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
> Link time is of course better.
> But if there is a syscall (like the one used by setarch) we could call it
> and reexec.
> Using setenv("DYLD_NO_PIE")+reexec looks gross to me.
There's posix_spawnattr_setflags() that can do the job
(http://reverse.put.as/2011/08/11/how-gdb-disables-aslr-in-mac-os-x-lion/),
but the necessary flag appeared only in Lion.
To the best of my
2011 Dec 09
1
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...R is controlled by the
> DYLD_NO_PIE env var, which is read by the dynamic loader.
> The third is Lion, which does not support DYLD_NO_PIE, but instead
> supports a flag I've mentioned above. I suppose further Mac OS
> releases will support only this way.
>
> There also is the MH_PIE bit in the Mach-O header, which we can flip
> to disable ASLR. But I'm not sure whether it won't disable the PIE
> behavior at all.
> Also, we'll need some special tool for that.
>
> > 2. doing setenv+reexec. This will be a debugging nightmare for us and
> for
>...
2011 Dec 09
2
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
...isableAslr function that should disable the
>> address space randomization.
>> This is now implemented for Mac OS 10.6 only.
>> In order to do this we add DYLD_NO_PIE=1 to the env and restart the
>> program.
>>
>> Next steps to be done are:
>> -- check for MH_PIE bit -- if it is 0, we don't need to disable anything;
>> -- use posix_spawnattr_setflags() to set the _POSIX_SPAWN_DISABLE_ASLR
>> on 10.7
>> -- disable ASLR on Linux, if needed.
>>
>> --
>> Alexander Potapenko
>> Software Engineer
>> Google Mos...
2011 Dec 09
4
[LLVMdev] [PATCH] Add the disable_aslr option that will disable the address space layout randomization under AddressSanitizer on 10.6
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