You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for raising this issue. I do not believe this is a bug in Go, this is just the way C works. However, it should be noted that as you've freed that memory you are into the area of underfined behaviour, after which, there are no guarentees.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
i study and write the cgo code, i free the pointer but i still can use it ,why?
my code
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you expect to see?
panic because use the free pointer
What did you see instead?
The text was updated successfully, but these errors were encountered: