From 1ab55a3f047502d8d59616c823facb7cd3ded487 Mon Sep 17 00:00:00 2001 From: Austin Clements Date: Tue, 17 Feb 2015 15:01:43 -0500 Subject: [PATCH] runtime: fix runtime-gdb_test on arm Apparently when ARM stops at a GDB breakpoint, it appears to be in syscall.Syscall. The "info goroutines" test expected it to be in a runtime function. Since this isn't fundamental to the test, simply tweak the test's regexp to make sure "info goroutines" prints some running goroutine with an active M, but don't require it to be in any particular function. Change-Id: Iba2618b46d3dc49cef62ffb72484b83ea7b0317d Reviewed-on: https://go-review.googlesource.com/5060 Reviewed-by: Dave Cheney --- src/runtime/runtime-gdb_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/runtime/runtime-gdb_test.go b/src/runtime/runtime-gdb_test.go index a946749f47..a926f5fb85 100644 --- a/src/runtime/runtime-gdb_test.go +++ b/src/runtime/runtime-gdb_test.go @@ -75,7 +75,7 @@ func TestGdbPython(t *testing.T) { blocks[string(subs[1])] = string(subs[2]) } - infoGoroutinesRe := regexp.MustCompile(`\d+\s+running\s+runtime`) + infoGoroutinesRe := regexp.MustCompile(`\*\s+\d+\s+running\s+`) if bl := blocks["info goroutines"]; !infoGoroutinesRe.MatchString(bl) { t.Fatalf("info goroutines failed: %s", bl) } -- 2.50.0