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: SIGSEGV in mmap_trampoline on openbsd-386-64 builder #46080

Open
bcmills opened this issue May 10, 2021 · 3 comments
Open

runtime: SIGSEGV in mmap_trampoline on openbsd-386-64 builder #46080

bcmills opened this issue May 10, 2021 · 3 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented May 10, 2021

2021-05-07T20:56:39-f05e912/openbsd-386-64

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x2 addr=0x6e35a000 pc=0x80aa221]

runtime stack:
runtime.throw({0x8268bef, 0x2a})
	/tmp/workdir/go/src/runtime/panic.go:1198 +0x64
runtime.sigpanic()
	/tmp/workdir/go/src/runtime/signal_unix.go:719 +0x22b
runtime.mmap_trampoline()
	/tmp/workdir/go/src/runtime/sys_openbsd_386.s:293 +0x61

As far as I can tell, mmap_trampoline was added to the openbsd/386 configuration 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.)

@bcmills
Copy link
Member Author

@bcmills bcmills commented May 10, 2021

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).

@bcmills
Copy link
Member Author

@bcmills bcmills commented May 10, 2021

I wonder if this is a symptom of a missed error check somewhere when the program is out of memory — the gcimporter test seems to be particularly memory-intensive (#45931).

@jrick
Copy link
Contributor

@jrick jrick commented May 10, 2021

all of these failures have os/exec.(*Cmd).Run in the trace. Related to #34988?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants