Hi Jan, I am a beginner with GO and cgo, and have never dealt with C corruption issues. Do you have commands or a blog post or something else where I can read about it and follow the steps. Being a beginner, I have to read and understand the stuff before applying it.
Thanks, Nitish On Sun, Jul 14, 2019 at 8:39 PM Jan Mercl <0xj...@gmail.com> wrote: > On Sun, Jul 14, 2019 at 5:03 PM Nitish Saboo <nitish.sabo...@gmail.com> > wrote: > > > Can some please share the details of tools or Debug options to debug the > following error in cgo: > > Log allocations, log frees. From the log you'll know at which line of > code the error was triggered. > > 'Log' can be as simple as printing to stdout/stderr. > > After you'll detect the error triggering location, log a stack trace > at that point. The pre-mortem (last logged) stack trace should be > helpful, hopefully. > -- 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/CALjMrq42YjufRs3Q%3D2pw-jMPKS%2BR8VBA3Em4_ieW3EwJx0QnWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
