Open RickMu opened 6 years ago
Because Go is garbage collected, and the garbage collector can run concurrently to any executing C code, they made the pointer semantics stricter at some point to avoid use-after-free bugs. Passing GODEBUG=cgocheck=0
in the environment disables these checks so that old code continues to work. I tried to address the issue in #167 but unfortunately I never managed to completely fix the problem.
Hey I'm using Go1.9 and is experiencing a CGO Pointer Error. I think this is a reference to #129, but I don't understand how
is a temporary fix