On 7/13/19, Nitish Saboo <nitish.sabo...@gmail.com> wrote: > Hi Ian, > > Apologies for not being very descriptive with the issue.I will try to be > more clear from next time. > Can you please clarify the following that you had mentioned in the previous > conversation of this email: > >> 3)Is it possible that one Go routine has already freed up the address > that the other Go routine is trying to free and that is causing this > 'fatal error: bin/main': double free or corruption (fasttop)' > > Yes, that is possible. It won't happen with the code I see above but > I have no idea what the rest of your code is doing. > > How can it not happen with this particular code mentioned ?I did not > understand this point. > Can you please clarify this point ? > > Thans, > Nitish > > On Fri, Jul 12, 2019 at 11:42 PM Ian Lance Taylor <i...@golang.org> wrote: > >> On Fri, Jul 12, 2019 at 10:53 AM Nitish Saboo <nitish.sabo...@gmail.com> >> wrote: >> > >> > Thanks for pointing it out.I am a beginner with Go and CGO and have >> never worked on corruption issues with C. >> > I am familiar with python and Java.So just seeking help from the >> > experts >> to find the pain points that should be looked into. >> > Hence, asking questions to Ian as in where all I should look for the >> corruption issues. >> >> From my perspective, it's kind of like you have a broken clock, and >> you are showing us a photo of the clock face, and asking how to fix >> the clock. We don't know. The clock face looks OK. The problem is >> most likely inside the clock, but we can't see that. Only you can see >> that. >> >> Ian >> > > --
Hi Nitish, you won't be able to get help, unless you show the code with the reported behavior. Please work on creating a small (<100 lines) self-contained, executable reproduction case. That's most probably a significant amount of work. If this type of error happened to anybody else, he or she would have to do this work him or herself as well. To be clear: that work must be done. Without that there is no step 2 or better description or any help. The good news is that during that work, you might find the cause of the error and even if not, you'll learn a lot about the environment you are trying to create a program in. When you are ready please share the result. Also please note that for sharing code, links to gist.github.com or play.golang.org are preferred. Code snippets are not enough. Better descriptions are not enough. Please don't ignore Ian's clock analogy, it's very good. cheers -- 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/CA%2Bctqrr6Wbw82QAFrLg-Gb9g%3DMi32uA9xt1otZW%3Ddv9y-KcoWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
