runtime: seg fault on Darwin in GC while under debugger #28373
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Comments
bradfitz
changed the title
bradfitz
added
the
NeedsInvestigation
|
/cc @aclements |
|
cc more owners, to see if someone can look into this: @rsc @RLH @randall77 A very similar error is failing all linux-arm-arm5spacemonkey builds as well: |
|
A potentially related issue (also getting segment violations): #27660 |
|
Here is a complete stack-trace of all threads when it panics: |
|
I also have the same behavior with 1.11.2 |
|
@robaho can you confirm this issue with 1.17.x ? |
davecheney
added
WaitingForInfo
|
It's been 4 years... but I did try and reproduce. I was unable to reproduce the crash. However, there seems to be an issue with the debugger/runtime where "stepping out" from the proc.go assembly support code "locks" the process and it makes no progress, nor is it able to be interrupted (manual break) again. |
|
Specifically stepping out from gopark() |
seankhliao
added
WaitingForInfo
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: