From 38d9b2a3a942892193195a6912ab23cdaff23e20 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sun, 7 Jun 2015 23:42:03 -0400 Subject: [PATCH] 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 Run-TryBot: Austin Clements --- src/runtime/mbitmap.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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)) -- 2.50.0