Yes, the problem is solved with the help of Tamás Gulácsi <https://groups.google.com/d/msg/golang-nuts/sO4I6Fk73Bw/gK6Q9ShOBgAJ>, and I'm trying to dig out the reason of my mistake there.
Thank you all! On Tuesday, February 26, 2019 at 1:40:40 PM UTC+8, Jan Mercl wrote: > > > On Tue, Feb 26, 2019 at 4:36 AM <yang...@gmail.com <javascript:>> 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.
