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

runtime: TestGdbLoadRuntimeSupport fails on non intel platforms #9820

Open
davecheney opened this Issue Feb 10, 2015 · 8 comments

Comments

Projects
None yet
5 participants
@davecheney
Contributor

davecheney commented Feb 10, 2015

runtime.TestGdbLoadRuntimeSupport does not pass on linux/arm or linux/ppc64le. In both cases the error is the same

--- FAIL: TestGdbLoadRuntimeSupport (1.98s)
    runtime-gdb_test.go:59: warning: Missing auto-load scripts referenced in section .debug_gdb_scripts
        of file /tmp/go-build302202449/a.exe
        Use `info auto-load python-scripts [REGEXP]' to list them.
FAIL
FAIL    runtime 64.538s

@davecheney davecheney added this to the Go1.5 milestone Feb 10, 2015

@davecheney

This comment has been minimized.

Contributor

davecheney commented Feb 10, 2015

This is failing because in environments where $GOROOT is not deducible (golang.org/x/build/cmd/builder for example) we're substituting some default path.

From a working tree that one of my builders was building at the time:

[root@alarm bin]# readelf -x 20 /root/workspace/nacl-arm-cheney-e6fbce3596c1/go/bin/gofmt 

Hex dump of section '.debug_gdb_scripts':
  0x00000000 012f7573 722f6c6f 63616c2f 676f2f73 ./usr/local/go/s
  0x00000010 72632f72 756e7469 6d652f72 756e7469 rc/runtime/runti
  0x00000020 6d652d67 64622e70 7900              me-gdb.py.

If I had to guess, the linux builders which are passing have a copy of Go 1.4 in /usr/local/go and are using that for $GOBOOTSTRAP_ROOT

@minux

This comment has been minimized.

Member

minux commented Feb 10, 2015

@bradfitz

This comment has been minimized.

Member

bradfitz commented Feb 10, 2015

No need to guess. Our builder environments are described with scripts to hermetically reproduce them. Just look in x/builder/env.

@minux

This comment has been minimized.

Member

minux commented Feb 10, 2015

@davecheney

This comment has been minimized.

Contributor

davecheney commented Feb 10, 2015

But why do we set it to /usr/local/go during a build that we know will be
built in a working directory?
On 10 Feb 2015 11:40, "Minux Ma" notifications@github.com wrote:

Aha, that's because we set GOROOT_FINAL in builders.


Reply to this email directly or view it on GitHub
#9820 (comment).

@minux

This comment has been minimized.

@davecheney davecheney self-assigned this Feb 10, 2015

@josharian

This comment has been minimized.

Contributor

josharian commented Feb 12, 2015

This is failing for me on OS X as well:

$ go test runtime -v -run=TestGdbLoadRuntimeSupport
=== RUN TestGdbLoadRuntimeSupport
--- FAIL: TestGdbLoadRuntimeSupport (0.25s)
    runtime-gdb_test.go:59: 
FAIL
exit status 1
FAIL    runtime 0.250s
@rsc

This comment has been minimized.

Contributor

rsc commented Jul 21, 2015

I think we're not going to get to this for Go 1.5.

@rsc rsc modified the milestones: Unplanned, Go1.5 Jul 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment