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/CAA40n-WiH80yMs5eCy41umC36uwKCBk%2BOSjeOGzZ%2B4DCPt8d0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
