From: Russ Cox <rsc@golang.org>
Date: Wed, 6 Aug 2014 18:50:09 +0000 (-0400)
Subject: runtime: turn off 'unexpected return pc' print on arm traceback
X-Git-Tag: go1.4beta1~921
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=e5e547c71f72722ca5fdd8ee67cf75f99ee586cf;p=gostls13.git

runtime: turn off 'unexpected return pc' print on arm traceback

It can happen legitimately if a profiling signal arrives at just the wrong moment.
It's harmless.

Fixes #8153.

LGTM=minux
R=golang-codereviews, minux
CC=golang-codereviews, iant, r
https://golang.org/cl/118670043
---

diff --git a/src/pkg/runtime/traceback_arm.c b/src/pkg/runtime/traceback_arm.c
index 757c1c39a3..778d95a28b 100644
--- a/src/pkg/runtime/traceback_arm.c
+++ b/src/pkg/runtime/traceback_arm.c
@@ -128,9 +128,14 @@ runtime·gentraceback(uintptr pc0, uintptr sp0, uintptr lr0, G *gp, int32 skip,
 				frame.lr = *(uintptr*)frame.sp;
 			flr = runtime·findfunc(frame.lr);
 			if(flr == nil) {
-				runtime·printf("runtime: unexpected return pc for %s called from %p\n", runtime·funcname(f), frame.lr);
-				if(callback != nil)
+				// This happens if you get a profiling interrupt at just the wrong time.
+				// In that context it is okay to stop early.
+				// But if callback is set, we're doing a garbage collection and must
+				// get everything, so crash loudly.
+				if(callback != nil) {
+					runtime·printf("runtime: unexpected return pc for %s called from %p\n", runtime·funcname(f), frame.lr);
 					runtime·throw("unknown caller pc");
+				}
 			}
 		}