Ian Lance Taylor be1ef46775 runtime: add optional expensive check for invalid cgo pointer passing ... If you set GODEBUG=cgocheck=2 the runtime package will use the write barrier to detect cases where a Go program writes a Go pointer into non-Go memory. In conjunction with the existing cgo checks, and the not-yet-implemented cgo check for exported functions, this should reliably detect all cases (that do not import the unsafe package) in which a Go pointer is incorrectly shared with C code. This check is optional because it turns on the write barrier at all times, which is known to be expensive. Update #12416. Change-Id: I549d8b2956daa76eac853928e9280e615d6365f4 Reviewed-on: https://go-review.googlesource.com/16899 Reviewed-by: Russ Cox <rsc@golang.org>		2015-11-16 18:39:06 +00:00
..
err1.go
err2.go
err3.go
issue7757.go
issue8442.go
issue11097a.go
issue11097b.go
ptr.go	runtime: add optional expensive check for invalid cgo pointer passing	2015-11-16 18:39:06 +00:00
test.bash	cmd/cgo, runtime: add checks for passing pointers from Go to C	2015-11-10 22:22:10 +00:00