Thankyou Ian, I did try a few runs with GODEBUG set to "cgocheck=2" and just the "normal" errors (bad Go heap ptr, and sweep increased allocation) occurred. I'm assuming I would have seen a different kind of panic if it had detected something.
Like I mentioned in the last post, we are very careful not to pass Go memory to with one exception where we pass a pointer to a Go uint32 that we expect to be filled in by the call. My understanding is this is permitted (cgo does not complain though it is very quick to complain if I try to pass the address of a string or byte array or structure). -- 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/3e71a176-ef6f-4fad-b282-0318d47fda4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
