From: Russ Cox <rsc@golang.org>
Date: Mon, 8 Jun 2015 03:42:03 +0000 (-0400)
Subject: runtime: diagnose invalid pointers during GC
X-Git-Tag: go1.5beta2~24
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=38d9b2a3a942892193195a6912ab23cdaff23e20;p=gostls13.git

runtime: diagnose invalid pointers during GC

For #9880. Let's see what breaks.

Change-Id: Ic8b99a604e60177a448af5f7173595feed607875
Reviewed-on: https://go-review.googlesource.com/10818
Reviewed-by: Austin Clements <austin@google.com>
Run-TryBot: Austin Clements <austin@google.com>
---

diff --git a/src/runtime/mbitmap.go b/src/runtime/mbitmap.go
index ef17409ebe..b9b52a7bc4 100644
--- a/src/runtime/mbitmap.go
+++ b/src/runtime/mbitmap.go
@@ -201,7 +201,7 @@ func heapBitsForObject(p uintptr) (base uintptr, hbits heapBits, s *mspan) {
 		// The following ensures that we are rigorous about what data
 		// structures hold valid pointers.
 		// TODO(rsc): Check if this still happens.
-		if false {
+		if true {
 			// Still happens sometimes. We don't know why.
 			printlock()
 			print("runtime:objectstart Span weird: p=", hex(p), " k=", hex(k))