runtime: SIGSEGV in mmap_trampoline on openbsd-386-64 builder #46080
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
OS-OpenBSD
Milestone
Comments
bcmills
added
OS-OpenBSD
NeedsInvestigation
|
This may be a newly-changed failure mode for an existing bug: the other stack traces involved are very similar to #36563 (CC @stamblerre @matloob). |
|
I wonder if this is a symptom of a missed error check somewhere when the program is out of memory — the |
|
all of these failures have os/exec.(*Cmd).Run in the trace. Related to #34988? |
|
While I don't see anymore https://build.golang.org/log/548414383c6f14e6524f77ac7e79f32af96334b7 In fact almost every openbsd-386-64 failure on https://build.golang.org/?repo=golang.org%2fx%2ftools right now is some variation of this SIGSEGV failure. Quite notably, every crash I've seen so far is while running |
|
I managed to reproduce a crash on a gomote first try: (Per @bcmills I'm certainly not holding modules right here, but it works...) |
|
I've been unable to get this to reproduce more than once on a gomote, it only crashes the very first time it runs. So always run in a new gomote. :) #!/bin/bash
MOTE=$(gomote create openbsd-386-64)
echo ${MOTE?}
GOROOT=$(pwd) gomote push ${MOTE?}
GOROOT=$(pwd) gomote run ${MOTE?} ./go/src/make.bash
GOROOT=$(pwd) gomote run -e GOPATH=/tmp/workdir/gopath ${MOTE?} /tmp/workdir/go/bin/go get golang.org/x/tools
GOROOT=$(pwd) gomote run -e GOPATH=/tmp/workdir/gopath -dir /tmp/workdir/gopath/pkg/mod/golang.org/x/tools@v0.1.3 -e PATH=/tmp/workdir/go/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin ${MOTE?} /tmp/workdir/go/bin/go test -short golang.org/x/tools/... |
|
I believe I have just experienced something similar to #46080 (comment) on darwin (without any mention of |
pmalek-sumo
pushed a commit
to SumoLogic/sumologic-otel-collector
that referenced
this issue
Jul 2, 2021
Due to a beta toolchain bug [1] don't use go1.17-beta1 for darwin builds, tests and release binaries (to release for all OSes using the same toolchain). [1]: golang/go#46080 (comment)
|
@pmalek-sumo yours looks like #46645. Could you try updating golang.org/x/sys ? Thanks. |
|
@cherrymui Thanks! Adding the following replace helped |
|
@pmalek-sumo, a |
|
@bcmills Why specifically is that not appropriate here? I'm using it because of the way the config for https://github.com/open-telemetry/opentelemetry-collector-builder is structured i.e. the code is generated based on it. |
|
@pmalek-sumo, the In contrast, the
|
|
Thanks for the explanation! We might need to rethink then the approach in the config file then and use |
|
Change https://golang.org/cl/357370 mentions this issue: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2021-05-07T20:56:39-f05e912/openbsd-386-64
As far as I can tell,
mmap_trampolinewas added to theopenbsd/386configuration in CL 287653 for #36435 (CC @4a6f656c @cherrymui), so this looks like a regression in Go 1.17 (CC @golang/release).(Note that that change only affects
openbsd/386— which is not a first-class port — so this doesn't need to be a release-blocker.)The text was updated successfully, but these errors were encountered: