I noticed go 1.1 beta sometimes fails to detect deadlock.
This happened in a few occasions where I forgot to Unlock an RWMutex. When
compiled with gc 1.0.3, the runtime properly paniced with "throw: all
goroutines are asleep - deadlock!". With go 1.1 beta, the program just
hung. This already happened on go tip between 1.0.3 and 1.1 beta. I am
running Linux x64.
My project (code.google.com/p/mx3) is rather large and I have not been able
to produce a minimal example with the same erratic behavior. I.e., a
minimal program that locks an RWMutex twice properly throws deadlock even
with go 1.1.
I must add that I call C code, and occasionally use the package "unsafe".
However, I have never experienced segfaults or "unexpected fault address"
panics. So I would be surprised if this were a memory corruption issue.
Did anyone else experience such issue?
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.