Oh, we've got another confirmed case of the scary runtime error. I guess 
now the question is, does anybody know of any memory corruption bugs in 
macOS and go1.15.5? I didn't see anything obvious.


runtime: gp: gp=0xc000802900, goid=0, gp->atomicstatus=0
runtime: g: g=0xc000602480, goid=0, g->atomicstatus=0
fatal error: bad g->status in ready

https://gist.github.com/awoods187/e9289c706ddc529034368fd3a2a25323

On Wednesday, March 24, 2021 at 10:02:20 PM UTC-4 awer...@gmail.com wrote:

> A situation has arisen a few times lately where we've seen segfaults that 
> have strange looking address values. Another thing that makes the situation 
> confusing is that the memory referenced by the stack trace should have been 
> allocated at init time. This seems to only be happening on macOS. The code 
> in question was built using go1.15.5 on x86_64-apple-darwin20.3.0. We 
> don't have a reliable repro but it has happened more than once. A user did 
> report seeing an odd message involving `g->` or so they claim. From my 
> sleuthing, the only code which could throw that message would be: 
> https://github.com/golang/go/blob/go1.15.5/src/runtime/proc.go#L703. 
>
> Anyway, this all smells of memory corruption to me but I would love 
> somebody to confirm my feeling that that fault address feels bogus. Is 
> there any non-corruption reason why one might see this sort of fault?
>
> unexpected fault address 0xfffffff800000019
> fatal error: fault
> [signal SIGSEGV: segmentation violation code=0x1 addr=0xfffffff800000019 
> pc=0x5658770]
>
> goroutine 2093790 [running]:
> runtime.throw(0x865aaf3, 0x5)
>       /usr/local/opt/go/libexec/src/runtime/panic.go:1116 +0x72 
> fp=0xc0338bdd18 sp=0xc0338bdce8 pc=0x403c7b2
> runtime.sigpanic()
>       /usr/local/opt/go/libexec/src/runtime/signal_unix.go:749 +0x3e5 
> fp=0xc0338bdd48 sp=0xc0338bdd18 pc=0x40532e5
>
> Cockroach is tracking this in 
> https://github.com/cockroachdb/cockroach/issues/62283. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/2226ea92-4d9b-4ff9-a441-fa3ac38acb9dn%40googlegroups.com.

Reply via email to