-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: -msan failure when rebuilding runtime/cgo with -fsanitize=memory #13815
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.
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
Comments
On GNU/Linux you need to use at least clang 3.8. This should be documented but I'm not sure where to do it. |
go test -msan
fails with use-of-uninitialized-value
I'm able to reproduce this with clang 3.8 as well. It appears the magic that reproduces it is:
I'm using I'm using
|
Thanks for the reproduction instructions. I will send a CL to fix this. |
CL https://golang.org/cl/18263 mentions this issue. |
The go tool used to avoid passing -fsanitize=memory when building runtime/cgo. That was originally to avoid an msan error, but that error was fixed anyhow for issue #13815. And building runtime/cgo with -fsanitize=memory corrects the handling of the context traceback function when the traceback function itself is built with -fsanitize=memory. Change-Id: I4bf5c3d21de6b2eb540600435ae47f5820d17464 Reviewed-on: https://go-review.googlesource.com/24855 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
foo_test.go:
Running under
lldb
didn't reveal much other than the involvement of cgo (I had to build the executable to getimage lookup
to work):Some system details:
Note that I had to use:
cc @ianlancetaylor
The text was updated successfully, but these errors were encountered: