I just had a fairly strange not reproducible panic. I have no idea whether
this could be a go bug or if the C library I am using is buggy. In case it
looks like a go bug I should probably post this on the issue tracker. Does
anyone have an idea whether this is useful or if I should just forget about
it? This is what the bug report would look like:
I build and ran a go program whose code I unfortunately can't share. The
program uses a go library called def (see stacktrace) which makes extensive
use of cgo. The line where it panics "def/instance.go:353" contains only an
assignment. The assignment is of the form *X.Y, where Y is a pointer to
space on the C heap that is allocated in the previous line.
This happened once and never again. The program and go library are strictly
single threaded. I don't know much about the C code around it though.
### What version of Go are you using (`go version`)?
$ go version
go version go1.7.3 linux/amd64
### What operating system and processor architecture are you using (`go
$ go env
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0
runtime: writebarrierptr *0x7fbca8000960 = 0x1
fatal error: bad pointer in write barrier
goroutine 1 [running]:
/usr/lib/go-1.7/src/runtime/mbarrier.go:152 +0x7b fp=0xc42003dd50
/home/florian/go/src/def/instance.go:353 +0xbea fp=0xc42003deb0
/home/florian/go/src/program/main.go:35 +0x27a fp=0xc42003df58
/usr/lib/go-1.7/src/runtime/proc.go:183 +0x1f4 fp=0xc42003dfb0
/usr/lib/go-1.7/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42003dfb8
goroutine 17 [syscall, locked to thread]:
goroutine 5 [syscall]:
runtime.CPUProfile(0x0, 0x0, 0x0)
created by runtime/pprof.StartCPUProfile
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.