From b307910b6e0695a1bf972cb3970dd49a652d5a43 Mon Sep 17 00:00:00 2001 From: Austin Clements Date: Mon, 21 Sep 2015 11:49:52 -0400 Subject: [PATCH] runtime: fix offset in invalidptr panic message Change-Id: I00e1eebbf5e1a01c8fad5ca5324aa8eec1e4d731 Reviewed-on: https://go-review.googlesource.com/14792 Reviewed-by: Rick Hudson --- 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 6998b14e7a..e7319c10de 100644 --- a/src/runtime/mbitmap.go +++ b/src/runtime/mbitmap.go @@ -225,7 +225,7 @@ func heapBitsForObject(p, refBase, refOff uintptr) (base uintptr, hbits heapBits } print("idx=", hex(idx), " span.start=", hex(s.start<<_PageShift), " span.limit=", hex(s.limit), " span.state=", s.state, "\n") if refBase != 0 { - print("runtime: found in object at *(", hex(refBase), "+", hex(off), ")\n") + print("runtime: found in object at *(", hex(refBase), "+", hex(refOff), ")\n") gcDumpObject("object", refBase, refOff) } throw("found bad pointer in Go heap (incorrect use of unsafe or cgo?)") -- 2.48.1