There is an address sanitizer in gcc too. On Thursday, December 15, 2016 at 10:15:23 PM UTC+3, Pablo Rozas-Larraondo wrote: > > Thanks Ian, > > So if I understand it well, this involves using clang compiler instead of > the default gcc when building Go code that uses cgo. I'll do some research > on how to do this. > > Cheers, > Pablo > > On Wed, Dec 14, 2016 at 5:36 PM, Ian Lance Taylor <ia...@golang.org > <javascript:>> wrote: > >> On Wed, Dec 14, 2016 at 4:57 PM, Pablo Rozas Larraondo >> <p.rozas....@gmail.com <javascript:>> wrote: >> > >> > I've seen this question asked before in the mail list but with no clear >> > answers. I'm just asking it again in case someone has come up with a >> new way >> > of doing this: >> > >> > Does anyone know about a good tool or method to detect memory leaks >> > happening on C code being called by cgo? >> >> clang's address sanitizer can do memory leak detection. I have not >> tried that with Go myself, but I suggest starting with that to see if >> you can make it work. >> >> Ian >> > >
-- 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.
