On Fri, Sep 22, 2023 at 9:15 AM Shivaram Lingamneni <[email protected]> wrote: > > I'm having difficulty understanding how this code could produce a nil > dereference, unless some runtime assumptions are being violated (maybe the > string pointer and length are out of sync due to a data race)?
I agree: this looks like some form of memory corruption. Run the code under the race detector. Look closely at any uses of cgo or the unsafe package. Ian -- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcW29rf5C2ieFN58A0C8o7f9WBTXLPc6Fxd7o_Z7s9XTbQ%40mail.gmail.com.
