>
> I am a beginner with GO and cgo, and have never dealt with C corruption
> issues.
>
> First, I would try really hard to find a pure go solution to your problem,
or next best, a solution that uses a 3rd party go package that handles the
cgo for you. I understand that this may not be
On Mon, 15 Jul 2019 10:55:19 +0530
Nitish Saboo wrote:
> 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
Internet is full of C and C debugging tutorials.
Thanks Kurtis.Will try these options.
Yes, now I remember you had given the same options on a different thread.
It just skipped my mind because of the mail conversation.
Thanks,
Nitish
On Mon, Jul 15, 2019 at 10:55 AM Kurtis Rader wrote:
> As I wrote in a reply on a different thread that has
As I wrote in a reply on a different thread that has the same purpose as
this one...
When debugging memory management problems in C/C++ code there are many
tools to assist in understanding the problem.
The first, and usually easiest to use is to enable your platform "debug"
version of the malloc
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
On Sun, Jul 14, 2019 at 5:03 PM Nitish Saboo 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
Hi,
Can some please share the details of tools or Debug options to debug the
following error in cgo:
Error in `bin/main': double free or corruption (fasttop)
Thanks,
Ntish
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from
