On Thu, Dec 15, 2016 at 12:57 AM, Pablo Rozas Larraondo
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
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
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 wrote:
> On Wed, Dec 14, 2016 at 4:57 PM, Pablo Ro
On Wed, Dec 14, 2016 at 4:57 PM, Pablo Rozas Larraondo
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 memor
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?
Cheers,
Pablo
--
You r
