Description
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.11
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
darwin, amd64, osx
What did you do?
running the application under the debugger, after stopping a while at a breakpoint and resuming, it panics
not sure it would help, but the stack trace may be obvious - the panic is in the GC
What did you expect to see?
What did you see instead?
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4fffff8 pc=0x1028007]
runtime stack:
runtime.throw(0x1b365fa, 0x2a)
/usr/local/Cellar/go/1.11/libexec/src/runtime/panic.go:608 +0x72
runtime.sigpanic()
/usr/local/Cellar/go/1.11/libexec/src/runtime/signal_unix.go:374 +0x288
runtime.spanOf(0xffffffffffffffff, 0x2df3421)
/usr/local/Cellar/go/1.11/libexec/src/runtime/mheap.go:519 +0x87
runtime.findObject(0xffffffffffffffff, 0x0, 0x0, 0x7fff7141f6c3, 0x4e, 0x4e)
/usr/local/Cellar/go/1.11/libexec/src/runtime/mbitmap.go:365 +0x2f
runtime.wbBufFlush1(0xc000044500)
/usr/local/Cellar/go/1.11/libexec/src/runtime/mwbbuf.go:252 +0xe5
runtime.wbBufFlush.func1()
/usr/local/Cellar/go/1.11/libexec/src/runtime/mwbbuf.go:195 +0x48
runtime.systemstack(0x700004ebbe88)
/usr/local/Cellar/go/1.11/libexec/src/runtime/asm_amd64.s:351 +0x66
runtime.mstart()
/usr/local/Cellar/go/1.11/libexec/src/runtime/proc.go:1229