[erlang-questions] Tracking memory leaks in NIF/Linkedin drivers with Valgrind (or anything else)
Mon Mar 18 18:11:26 CET 2013
On Mar 18, 2013, at 5:53 PM, Jon Schneider wrote:
>> ==59400== by 0x10000191F: main (in
>> ==59400== ERROR SUMMARY: 460 errors from 15 contexts (suppressed: 0 from
>> How can I distinguish between these falsy reported numbers and the real
> Isn't the information you require in the return
> address/function/executable reported even if this needs a little
> post-processing ?
Yet it is. But it's mixed with a lot of false positive (see crypto example).
And if I can avoid post-processing, that should be great.
>> Finally, is there any other way than Valgrind?
> Yes by instrumenting your code.
DTrace? SystemTap? How?
Can you elaborate with a concret example?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions