Elias Naur d24b57a6a1 runtime: handle SIGPIPE in c-archive and c-shared programs ... Before this CL, Go programs in c-archive or c-shared buildmodes would not handle SIGPIPE. That leads to surprising behaviour where writes on a closed pipe or socket would raise SIGPIPE and terminate the program. This CL changes the Go runtime to handle SIGPIPE regardless of buildmode. In addition, SIGPIPE from non-Go code is forwarded. Fixes #17393 Updates #16760 Change-Id: I155e82020a03a5cdc627a147c27da395662c3fe8 Reviewed-on: https://go-review.googlesource.com/32796 Run-TryBot: Elias Naur <elias.naur@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>		2016-11-18 01:19:11 +00:00
..
src	runtime: handle SIGPIPE in c-archive and c-shared programs	2016-11-18 01:19:11 +00:00
carchive_test.go	runtime: handle SIGPIPE in c-archive and c-shared programs	2016-11-18 01:19:11 +00:00
main2.c	runtime: handle SIGPIPE in c-archive and c-shared programs	2016-11-18 01:19:11 +00:00
main3.c	runtime: handle SIGPIPE in c-archive and c-shared programs	2016-11-18 01:19:11 +00:00
main4.c	misc/cgo: decrease test failure timeouts	2016-11-17 16:31:34 +00:00
main5.c	runtime: handle SIGPIPE in c-archive and c-shared programs	2016-11-18 01:19:11 +00:00
main_unix.c	misc/cgo/testcarchive: split main.c into unix and non-unix	2016-03-26 00:57:23 +00:00
main_windows.c	misc/cgo/testcarchive: split main.c into unix and non-unix	2016-03-26 00:57:23 +00:00
main.c	misc/cgo/testcarchive: split main.c into unix and non-unix	2016-03-26 00:57:23 +00:00