Go crash - misbehave between C and GO

Hi, @aotto1968, I see what you mean, but it’s been my experience that Go has (to me) an idiosyncratic handling of NULL/nil pointers (consider this).

That being said, I’m curious why it’s an issue for you.