Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime: clang builder broken #12814

Closed
bradfitz opened this issue Oct 1, 2015 · 6 comments
Closed

runtime: clang builder broken #12814

bradfitz opened this issue Oct 1, 2015 · 6 comments
Labels
FrozenDueToAge

Comments

@bradfitz
Copy link
Contributor

bradfitz commented Oct 1, 2015

@ianlancetaylor's https://go-review.googlesource.com/#/c/15170/ broke the clang builder. (which for saving-money reasons isn't a trybot, since failures there are more rare now that we're mostly in Go...)

Failure is:
http://build.golang.org/log/a9043ae6a94865c40b47c457535a29c01a0f7449

##### ../misc/cgo/testsanitizers
FATAL: MemorySanitizer can not mmap the shadow memory.
FATAL: Make sure to compile with -fPIE and to link with -pie.
FATAL: Disabling ASLR is known to cause this error.
FATAL: If running under GDB, try 'set disable-randomization off'.
==19420==Process memory map follows:
    0x000000000000-0x200000000000   
    0x7f9c01070000-0x7f9c013c2000   
    0x7f9c013c2000-0x7f9c01544000   /lib/x86_64-linux-gnu/libc-2.13.so
    0x7f9c01544000-0x7f9c01744000   /lib/x86_64-linux-gnu/libc-2.13.so
    0x7f9c01744000-0x7f9c01748000   /lib/x86_64-linux-gnu/libc-2.13.so
    0x7f9c01748000-0x7f9c01749000   /lib/x86_64-linux-gnu/libc-2.13.so
    0x7f9c01749000-0x7f9c0174e000   
    0x7f9c0174e000-0x7f9c01763000   /lib/x86_64-linux-gnu/libgcc_s.so.1
    0x7f9c01763000-0x7f9c01963000   /lib/x86_64-linux-gnu/libgcc_s.so.1
    0x7f9c01963000-0x7f9c01964000   /lib/x86_64-linux-gnu/libgcc_s.so.1
    0x7f9c01964000-0x7f9c01966000   /lib/x86_64-linux-gnu/libdl-2.13.so
    0x7f9c01966000-0x7f9c01b66000   /lib/x86_64-linux-gnu/libdl-2.13.so
    0x7f9c01b66000-0x7f9c01b67000   /lib/x86_64-linux-gnu/libdl-2.13.so
    0x7f9c01b67000-0x7f9c01b68000   /lib/x86_64-linux-gnu/libdl-2.13.so
    0x7f9c01b68000-0x7f9c01be9000   /lib/x86_64-linux-gnu/libm-2.13.so
    0x7f9c01be9000-0x7f9c01de8000   /lib/x86_64-linux-gnu/libm-2.13.so
    0x7f9c01de8000-0x7f9c01de9000   /lib/x86_64-linux-gnu/libm-2.13.so
    0x7f9c01de9000-0x7f9c01dea000   /lib/x86_64-linux-gnu/libm-2.13.so
    0x7f9c01dea000-0x7f9c01df1000   /lib/x86_64-linux-gnu/librt-2.13.so
    0x7f9c01df1000-0x7f9c01ff0000   /lib/x86_64-linux-gnu/librt-2.13.so
    0x7f9c01ff0000-0x7f9c01ff1000   /lib/x86_64-linux-gnu/librt-2.13.so
    0x7f9c01ff1000-0x7f9c01ff2000   /lib/x86_64-linux-gnu/librt-2.13.so
    0x7f9c01ff2000-0x7f9c02009000   /lib/x86_64-linux-gnu/libpthread-2.13.so
    0x7f9c02009000-0x7f9c02208000   /lib/x86_64-linux-gnu/libpthread-2.13.so
    0x7f9c02208000-0x7f9c02209000   /lib/x86_64-linux-gnu/libpthread-2.13.so
    0x7f9c02209000-0x7f9c0220a000   /lib/x86_64-linux-gnu/libpthread-2.13.so
    0x7f9c0220a000-0x7f9c0220e000   
    0x7f9c0220e000-0x7f9c0222e000   /lib/x86_64-linux-gnu/ld-2.13.so
    0x7f9c0241e000-0x7f9c02427000   
    0x7f9c02428000-0x7f9c0242d000   
    0x7f9c0242d000-0x7f9c0242e000   /lib/x86_64-linux-gnu/ld-2.13.so
    0x7f9c0242e000-0x7f9c0242f000   /lib/x86_64-linux-gnu/ld-2.13.so
    0x7f9c0242f000-0x7f9c02430000   
    0x7f9c02430000-0x7f9c02741000   /tmp/go-build686805548/command-line-arguments/_obj/exe/msan
    0x7f9c02941000-0x7f9c0294a000   /tmp/go-build686805548/command-line-arguments/_obj/exe/msan
    0x7f9c0294a000-0x7f9c04da9000   
    0x7fff05fb0000-0x7fff05fd1000   [stack]
    0x7fff05ffc000-0x7fff05ffe000   [vdso]
    0x7fff05ffe000-0x7fff06000000   [vvar]
    0xffffffffff600000-0xffffffffff601000   [vsyscall]
==19420==End of process memory map.
exit status 77
2015/09/30 22:31:47 Failed: exit status 1
@ianlancetaylor
Copy link
Member

What version of clang are we running on the builder?

@bradfitz
Copy link
Contributor Author

bradfitz commented Oct 2, 2015

I don't know. See the env directory of x/build for the defininiton. (On phone)

@crawshaw crawshaw mentioned this issue Oct 2, 2015
Closed
@crawshaw
Copy link
Member

crawshaw commented Oct 2, 2015

clang-3.5 according to the Dockerfile

It predates http://llvm.org/viewvc/llvm-project?view=revision&revision=238109, which fixed a similar-looking failure in v8.

@bradfitz
Copy link
Contributor Author

bradfitz commented Oct 2, 2015

Is 3.5 something we want to continue to support? 3.0 is in Debian wheezy and 3.5 is in Debian jessie.

Can 3.5 just be detected and worked around, or have msan disabled in that environment?

@mewmew
Copy link
Contributor

mewmew commented Oct 9, 2015

I still get this error, but not sure if it is related to clang as I've also got GCC installed.

[~]$ gcc --version
gcc (GCC) 5.2.0

[~]$ clang --version
clang version 3.7.0 (tags/RELEASE_370/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix

[~]$ go version
go version devel +ae31599 Thu Oct 8 23:15:40 2015 +0000 linux/amd64

And the error is as follows:

##### ../misc/cgo/testsanitizers
FATAL: Code 0x55b1cb4d8e20 is out of application range. Non-PIE build?
FATAL: MemorySanitizer can not mmap the shadow memory.
FATAL: Make sure to compile with -fPIE and to link with -pie.
FATAL: Disabling ASLR is known to cause this error.
FATAL: If running under GDB, try 'set disable-randomization off'.
==21153==Process memory map follows:
    0x55b1cb3f6000-0x55b1cb6fa000   /tmp/go-build208042185/command-line-arguments/_obj/exe/msan
    0x55b1cb8f9000-0x55b1cb901000   /tmp/go-build208042185/command-line-arguments/_obj/exe/msan
    0x55b1cb901000-0x55b1cdd9c000   
    0x7f0a2addf000-0x7f0a2b131000   
    0x7f0a2b131000-0x7f0a2b2cc000   /usr/lib/libc-2.22.so
    0x7f0a2b2cc000-0x7f0a2b4cb000   /usr/lib/libc-2.22.so
    0x7f0a2b4cb000-0x7f0a2b4cf000   /usr/lib/libc-2.22.so
    0x7f0a2b4cf000-0x7f0a2b4d1000   /usr/lib/libc-2.22.so
    0x7f0a2b4d1000-0x7f0a2b4d5000   
    0x7f0a2b4d5000-0x7f0a2b4eb000   /usr/lib/libgcc_s.so.1
    0x7f0a2b4eb000-0x7f0a2b6ea000   /usr/lib/libgcc_s.so.1
    0x7f0a2b6ea000-0x7f0a2b6eb000   /usr/lib/libgcc_s.so.1
    0x7f0a2b6eb000-0x7f0a2b6ee000   /usr/lib/libdl-2.22.so
    0x7f0a2b6ee000-0x7f0a2b8ed000   /usr/lib/libdl-2.22.so
    0x7f0a2b8ed000-0x7f0a2b8ee000   /usr/lib/libdl-2.22.so
    0x7f0a2b8ee000-0x7f0a2b8ef000   /usr/lib/libdl-2.22.so
    0x7f0a2b8ef000-0x7f0a2b9ec000   /usr/lib/libm-2.22.so
    0x7f0a2b9ec000-0x7f0a2bbeb000   /usr/lib/libm-2.22.so
    0x7f0a2bbeb000-0x7f0a2bbec000   /usr/lib/libm-2.22.so
    0x7f0a2bbec000-0x7f0a2bbed000   /usr/lib/libm-2.22.so
    0x7f0a2bbed000-0x7f0a2bbf4000   /usr/lib/librt-2.22.so
    0x7f0a2bbf4000-0x7f0a2bdf3000   /usr/lib/librt-2.22.so
    0x7f0a2bdf3000-0x7f0a2bdf4000   /usr/lib/librt-2.22.so
    0x7f0a2bdf4000-0x7f0a2bdf5000   /usr/lib/librt-2.22.so
    0x7f0a2bdf5000-0x7f0a2be0d000   /usr/lib/libpthread-2.22.so
    0x7f0a2be0d000-0x7f0a2c00c000   /usr/lib/libpthread-2.22.so
    0x7f0a2c00c000-0x7f0a2c00d000   /usr/lib/libpthread-2.22.so
    0x7f0a2c00d000-0x7f0a2c00e000   /usr/lib/libpthread-2.22.so
    0x7f0a2c00e000-0x7f0a2c012000   
    0x7f0a2c012000-0x7f0a2c034000   /usr/lib/ld-2.22.so
    0x7f0a2c216000-0x7f0a2c21b000   
    0x7f0a2c229000-0x7f0a2c233000   
    0x7f0a2c233000-0x7f0a2c234000   /usr/lib/ld-2.22.so
    0x7f0a2c234000-0x7f0a2c235000   /usr/lib/ld-2.22.so
    0x7f0a2c235000-0x7f0a2c236000   
    0x7ffdda888000-0x7ffdda8a9000   [stack]
    0x7ffdda9ba000-0x7ffdda9bc000   [vvar]
    0x7ffdda9bc000-0x7ffdda9be000   [vdso]
    0xffffffffff600000-0xffffffffff601000   [vsyscall]
==21153==End of process memory map.
exit status 77

Please let me know if any other information is required.

@ianlancetaylor
Copy link
Member

@mewmew That looks like a different problem. Please open a new issue. Thanks.

@mewmew mewmew mentioned this issue Oct 10, 2015
Closed
@golang golang locked and limited conversation to collaborators Oct 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bradfitz @crawshaw @mewmew @ianlancetaylor @gopherbot