On Tue, Feb 26, 2019 at 4:36 AM <yangwu...@gmail.com> wrote: Yesterday you showed us an incorrect use of unsafe.Pointers while interacting with C. It might be the same/similar problem. The lines indicated in your post all allocate memory and may trigger GC, yes, but they per se are improbable to crash the process. I think the crash is caused by memory corruption which happened way before executing those lines.
Without a complete, self-contained, minimal reproducer it's next to impossible to see where is the problem rooted. -- -j -- 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. For more options, visit https://groups.google.com/d/optout.
