From b61b7d5e34573d5b303e3a3f223bdb6023847fb7 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Tue, 27 Mar 2012 12:22:19 -0400 Subject: runtime: work around false negative in deadlock detection Not a complete fix for issue 3342, but fixes the trivial case. There may still be a race in the instants before and after a scavenger-induced garbage collection. Intended to be "obviously safe": a call to runtime?gosched before main.main is no different than a call to runtime.Gosched at the beginning of main.main, and it is (or had better be) safe to call runtime.Gosched at any point during main. Update issue 3342. R=iant CC=golang-dev http://codereview.appspot.com/5919052 --- test/golden.out | 3 +++ 1 file changed, 3 insertions(+) (limited to 'test/golden.out') diff --git a/test/golden.out b/test/golden.out index 764f56196..376af8e53 100644 --- a/test/golden.out +++ b/test/golden.out @@ -15,6 +15,9 @@ == fixedbugs/ +=========== fixedbugs/bug429.go +throw: all goroutines are asleep - deadlock! + == bugs/ =========== bugs/bug395.go -- cgit v1.2.1