golang/go

runtime: failures with `fatal error: traceback did not unwind completely` on `openbsd/arm64`

Open

#62,182 opened on Aug 21, 2023

View on GitHub
 (21 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationOS-OpenBSDarch-arm64compiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

#!watchflakes
post <- goos == "openbsd" && goarch == "arm64" && log ~ `fatal error: traceback did not unwind completely`

(Pulled out from https://github.com/golang/go/issues/55167#issuecomment-1686446766, https://github.com/golang/go/issues/62105#issuecomment-1682814478, and https://github.com/golang/go/issues/62101#issuecomment-1682814436.)

Contributor guide

Research direction
Reproduce the failure on openbsd/arm64 by running the runtime stress tests. Inspect the crash dump to identify where the traceback fails to unwind. Focus on signal handling and goroutine stack at the point of crash.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
GoOpenBSD/ARM64Assembly
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30