aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2015-07-29 15:18:56 -0400
committerRuss Cox <rsc@golang.org>2015-07-29 21:37:55 +0000
commit4addec3aaa495acc7c111acfd0889d8a994bc9f2 (patch)
tree33e139d4a9057ff74dc74b42b0a3aff163d2ebd4
parent034a10d44c8f83d2c36ab4e242c14e9744c54949 (diff)
downloadgo-4addec3aaa495acc7c111acfd0889d8a994bc9f2.tar.gz
go-4addec3aaa495acc7c111acfd0889d8a994bc9f2.zip
runtime: reenable bad pointer check in GC
The last time we tried this, linux/arm64 broke. The series of CLs leading to this one fixes that problem. Let's try again. Fixes #9880. Change-Id: I67bc1d959175ec972d4dcbe4aa6f153790f74251 Reviewed-on: https://go-review.googlesource.com/12849 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Austin Clements <austin@google.com>
-rw-r--r--src/runtime/mbitmap.go2
1 files changed, 1 insertions, 1 deletions
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))