golang/go

cmd/link: static linking creates binaries that segfault when built with `-msan`

Open

#70,080 opened on Oct 28, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
NeedsFixcompiler/runtimehelp wanted

Description

Discovered during #70054. Don't know what's happening, but I'm adding skips in dist for now.

Contributor guide

Tech stack
go
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go linker internalsMSan instrumentationStatic linking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
5
Research direction
Investigate the segfault when building with msan and static linking. Refer to issue #70054 for discovery context. The current fix is adding skips in `dist` but a proper solution requires examining cmd/link and MSan instrumentation. Look at the linker's handling of memory sanitizer flags and static binary generation.