Commit 38d9b2a3 authored by Russ Cox's avatar Russ Cox

runtime: diagnose invalid pointers during GC

For #9880. Let's see what breaks.

Change-Id: Ic8b99a604e60177a448af5f7173595feed607875
Reviewed-on: https://go-review.googlesource.com/10818Reviewed-by: default avatarAustin Clements <austin@google.com>
Run-TryBot: Austin Clements <austin@google.com>
parent 7feb4249
...@@ -201,7 +201,7 @@ func heapBitsForObject(p uintptr) (base uintptr, hbits heapBits, s *mspan) { ...@@ -201,7 +201,7 @@ func heapBitsForObject(p uintptr) (base uintptr, hbits heapBits, s *mspan) {
// The following ensures that we are rigorous about what data // The following ensures that we are rigorous about what data
// structures hold valid pointers. // structures hold valid pointers.
// TODO(rsc): Check if this still happens. // TODO(rsc): Check if this still happens.
if false { if true {
// Still happens sometimes. We don't know why. // Still happens sometimes. We don't know why.
printlock() printlock()
print("runtime:objectstart Span weird: p=", hex(p), " k=", hex(k)) print("runtime:objectstart Span weird: p=", hex(p), " k=", hex(k))
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment