golang/go

runtime: externally linked programs don't detect deadlocks

Open

#29,322 opened on Dec 18, 2018

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

Repository metrics

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

Description

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

Yes (also master as of last week)

What operating system and processor architecture are you using (go env)?

What did you do?

Did go run -buildmode=pie with this:

package main

func main() {
	ch1 := make(chan string)
	ch2 := make(chan string)
	go func() {
		<-ch1
		ch2 <- "done"
	}()
	<-ch2
	ch1 <- "done"
}

What did you expect to see?

Process dies with the "all goroutines are asleep" message.

What did you see instead?

Not dead but forever sleeping.

Contributor guide

Research direction
Investigate why deadlock detection fails in externally linked programs. Focus on the runtime's deadlock detection signal (SIGURG) and the startTheWorld function. Compare behavior with and without buildmode=pie. Check if the signal handler is properly set up in externally linked executables.
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.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Goruntime internalscgo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20