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.

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/trace: TestTraceStress crashes with SIGBUS on freebsd-386-gce101 #9901

Closed
mikioh opened this issue Feb 17, 2015 · 2 comments
Closed
Milestone

Comments

@mikioh
Copy link
Contributor

mikioh commented Feb 17, 2015

$ go version
go version devel +82ee85e w/ change 4330

$ environment
trybot: freebsd-386-gce101, which runs freebsd/386 runtime on freebsd/amd64 kernel.

See See https://storage.googleapis.com/go-build-log/5c323c50/freebsd-386-gce101_fca8db55.log for further information.

The headline of dying message (SIGBUS) is as follows:

fatal error: unexpected signal during runtime execution
[signal 0xa code=0xc addr=0x28306000 pc=0x805ac86]

Not sure this is equivalent to #9729.

@dvyukov dvyukov added this to the Go1.5 milestone Feb 17, 2015
@dvyukov
Copy link
Member

dvyukov commented Feb 17, 2015

@RLH @aclements This seems to be more related to write barriers rather than tracing. TestTraceStress just stresses runtime well.

@bradfitz bradfitz changed the title runtime/pprof: TestTraceStress crashes with SUGBUS on freebsd-386-gce101 runtime/pprof: TestTraceStress crashes with SIGBUS on freebsd-386-gce101 Feb 17, 2015
@mikioh
Copy link
Contributor Author

mikioh commented Feb 24, 2015

Merged into #9953

@mikioh mikioh closed this as completed Feb 24, 2015
@mikioh mikioh changed the title runtime/pprof: TestTraceStress crashes with SIGBUS on freebsd-386-gce101 runtime/trace: TestTraceStress crashes with SIGBUS on freebsd-386-gce101 Jul 31, 2015
@golang golang locked and limited conversation to collaborators Aug 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants