search for: posix_spawnattr_setflag

On Dec 9, 2011, at 11:46 AM, Alexander Potapenko wrote: >> 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 knowledge, there's no link-time option that disables > ASLR but keeps PIE on Snow Leopard or Lion. > At t...

...ddress 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 part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/ll...

> 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 knowledge, there's no link-time option that disables ASLR but keeps PIE on Snow Leopard or Lion. At the moment we're using DYLD...

...t; 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 > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

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

...>> 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 >> > > _______________________________________________ > LLVM Developers mailing...

..._ZNSt3__16futureIvED1Ev 0000000000000000 DF *UND* 00000000000001f0 Base update_panels 0000000000000000 DF *UND* 0000000000000072 Base el_end 0000000000000000 DF *UND* 000000000000008b GLIBC_2.2.5 snprintf 0000000000000000 DF *UND* 0000000000000013 GLIBC_2.2.5 posix_spawnattr_setflags 0000000000000000 DF *UND* 00000000000000ef Base history_init 0000000000000000 DF *UND* 000000000000007e GLIBC_2.2.5 acos 0000000000000000 DF *UND* 0000000000000090 GLIBC_2.2.5 sscanf 0000000000000000 DF *UND* 000000000000002d GLIBC_2.2.5 closedir 0000000000000000...

Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB. I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...