<div dir="ltr">Can you open a separate bug with exact repro instructions? </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 20, 2015 at 2:47 PM, Greg Stark <span dir="ltr"><<a href="mailto:stark@mit.edu" target="_blank">stark@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hm, that bug has been closed as resolved but I still see the problem:<br>
<br>
$ clang --version<br>
clang version 3.8.0 (trunk 250848) (llvm/trunk 250846)<br>
Target: x86_64-unknown-linux-gnu<br>
Thread model: posix<br>
InstalledDir: /usr/local/bin<br>
<br>
<br>
configure:4042: ./conftest<br>
FATAL: Code 0x5615faea43f0 is out of application range. Non-PIE build?<br>
<span class="">FATAL: MemorySanitizer can not mmap the shadow memory.<br>
FATAL: Make sure to compile with -fPIE and to link with -pie.<br>
FATAL: Disabling ASLR is known to cause this error.<br>
FATAL: If running under GDB, try 'set disable-randomization off'.<br>
</span>==14645==Process memory map follows:<br>
0x5615fae87000-0x5615faf26000 /home/stark/src/pg/postgresql-master/conftest<br>
0x5615fb126000-0x5615fb12a000 /home/stark/src/pg/postgresql-master/conftest<br>
0x5615fb12a000-0x5615fd59d000<br>
0x7f86a64a3000-0x7f86a67f5000<br>
0x7f86a67f5000-0x7f86a6994000 /lib/x86_64-linux-gnu/<a href="http://libc-2.19.so" rel="noreferrer" target="_blank">libc-2.19.so</a><br>
0x7f86a6994000-0x7f86a6b94000 /lib/x86_64-linux-gnu/<a href="http://libc-2.19.so" rel="noreferrer" target="_blank">libc-2.19.so</a><br>
0x7f86a6b94000-0x7f86a6b98000 /lib/x86_64-linux-gnu/<a href="http://libc-2.19.so" rel="noreferrer" target="_blank">libc-2.19.so</a><br>
0x7f86a6b98000-0x7f86a6b9a000 /lib/x86_64-linux-gnu/<a href="http://libc-2.19.so" rel="noreferrer" target="_blank">libc-2.19.so</a><br>
0x7f86a6b9a000-0x7f86a6b9e000<br>
0x7f86a6b9e000-0x7f86a6bb4000 /lib/x86_64-linux-gnu/libgcc_s.so.1<br>
0x7f86a6bb4000-0x7f86a6db3000 /lib/x86_64-linux-gnu/libgcc_s.so.1<br>
0x7f86a6db3000-0x7f86a6db4000 /lib/x86_64-linux-gnu/libgcc_s.so.1<br>
0x7f86a6db4000-0x7f86a6db7000 /lib/x86_64-linux-gnu/<a href="http://libdl-2.19.so" rel="noreferrer" target="_blank">libdl-2.19.so</a><br>
0x7f86a6db7000-0x7f86a6fb6000 /lib/x86_64-linux-gnu/<a href="http://libdl-2.19.so" rel="noreferrer" target="_blank">libdl-2.19.so</a><br>
0x7f86a6fb6000-0x7f86a6fb7000 /lib/x86_64-linux-gnu/<a href="http://libdl-2.19.so" rel="noreferrer" target="_blank">libdl-2.19.so</a><br>
0x7f86a6fb7000-0x7f86a6fb8000 /lib/x86_64-linux-gnu/<a href="http://libdl-2.19.so" rel="noreferrer" target="_blank">libdl-2.19.so</a><br>
0x7f86a6fb8000-0x7f86a70b8000 /lib/x86_64-linux-gnu/<a href="http://libm-2.19.so" rel="noreferrer" target="_blank">libm-2.19.so</a><br>
0x7f86a70b8000-0x7f86a72b7000 /lib/x86_64-linux-gnu/<a href="http://libm-2.19.so" rel="noreferrer" target="_blank">libm-2.19.so</a><br>
0x7f86a72b7000-0x7f86a72b8000 /lib/x86_64-linux-gnu/<a href="http://libm-2.19.so" rel="noreferrer" target="_blank">libm-2.19.so</a><br>
0x7f86a72b8000-0x7f86a72b9000 /lib/x86_64-linux-gnu/<a href="http://libm-2.19.so" rel="noreferrer" target="_blank">libm-2.19.so</a><br>
0x7f86a72b9000-0x7f86a72c0000 /lib/x86_64-linux-gnu/<a href="http://librt-2.19.so" rel="noreferrer" target="_blank">librt-2.19.so</a><br>
0x7f86a72c0000-0x7f86a74bf000 /lib/x86_64-linux-gnu/<a href="http://librt-2.19.so" rel="noreferrer" target="_blank">librt-2.19.so</a><br>
0x7f86a74bf000-0x7f86a74c0000 /lib/x86_64-linux-gnu/<a href="http://librt-2.19.so" rel="noreferrer" target="_blank">librt-2.19.so</a><br>
0x7f86a74c0000-0x7f86a74c1000 /lib/x86_64-linux-gnu/<a href="http://librt-2.19.so" rel="noreferrer" target="_blank">librt-2.19.so</a><br>
0x7f86a74c1000-0x7f86a74d9000 /lib/x86_64-linux-gnu/<a href="http://libpthread-2.19.so" rel="noreferrer" target="_blank">libpthread-2.19.so</a><br>
0x7f86a74d9000-0x7f86a76d8000 /lib/x86_64-linux-gnu/<a href="http://libpthread-2.19.so" rel="noreferrer" target="_blank">libpthread-2.19.so</a><br>
0x7f86a76d8000-0x7f86a76d9000 /lib/x86_64-linux-gnu/<a href="http://libpthread-2.19.so" rel="noreferrer" target="_blank">libpthread-2.19.so</a><br>
0x7f86a76d9000-0x7f86a76da000 /lib/x86_64-linux-gnu/<a href="http://libpthread-2.19.so" rel="noreferrer" target="_blank">libpthread-2.19.so</a><br>
0x7f86a76da000-0x7f86a76de000<br>
0x7f86a76de000-0x7f86a76fe000 /lib/x86_64-linux-gnu/<a href="http://ld-2.19.so" rel="noreferrer" target="_blank">ld-2.19.so</a><br>
0x7f86a78d7000-0x7f86a78dc000<br>
0x7f86a78f2000-0x7f86a78fe000<br>
0x7f86a78fe000-0x7f86a78ff000 /lib/x86_64-linux-gnu/<a href="http://ld-2.19.so" rel="noreferrer" target="_blank">ld-2.19.so</a><br>
0x7f86a78ff000-0x7f86a7900000 /lib/x86_64-linux-gnu/<a href="http://ld-2.19.so" rel="noreferrer" target="_blank">ld-2.19.so</a><br>
0x7f86a7900000-0x7f86a7901000<br>
0x7fff98977000-0x7fff98998000 [stack]<br>
0x7fff989b2000-0x7fff989b4000 [vvar]<br>
0x7fff989b4000-0x7fff989b6000 [vdso]<br>
0xffffffffff600000-0xffffffffff601000 [vsyscall]<br>
==14645==End of process memory map.<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Sep 14, 2015 at 9:46 PM, Evgenii Stepanov<br>
<<a href="mailto:eugeni.stepanov@gmail.com">eugeni.stepanov@gmail.com</a>> wrote:<br>
> Yes, the kernel is too new.<br>
> This bug has a patch set that's compatible with the new kernel and<br>
> does not even require -pie:<br>
> <a href="https://llvm.org/bugs/show_bug.cgi?id=24155" rel="noreferrer" target="_blank">https://llvm.org/bugs/show_bug.cgi?id=24155</a><br>
> It breaks MSan ABI though, so we can not apply it upstream yet.<br>
><br>
><br>
> On Sat, Sep 12, 2015 at 3:31 PM, Kostya Serebryany via llvm-dev<br>
> <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br>
>> clang revision is good, but the kernel is probably too new.<br>
>> Evgenii can comment on that.<br>
>><br>
>> On Sat, Sep 12, 2015 at 3:23 PM, Greg Stark <<a href="mailto:stark@mit.edu">stark@mit.edu</a>> wrote:<br>
>>><br>
>>> On Sat, Sep 12, 2015 at 11:22 PM, Greg Stark <<a href="mailto:stark@mit.edu">stark@mit.edu</a>> wrote:<br>
>>> > Checked out a few days ago. It looks like r246697. I suppose I could<br>
>>> > try updating and rebuilding.<br>
>>><br>
>>> Sorry, svn log in the tools/clang directory shows r246702.<br>
>>><br>
>>><br>
>>> --<br>
>>> greg<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
>><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
greg<br>
</font></span></blockquote></div><br></div>