[erlang-questions] Tracking memory leaks in NIF/Linkedin drivers with Valgrind (or anything else)

Jon Schneider <>
Mon Mar 18 17:53:20 CET 2013


> /opt/r16b/usr/lib/erlang/erts-5.10.1/bin/beam.valgrind.smp)
> ==59400==    by 0x10000191F: main (in
> /opt/r16b/usr/lib/erlang/erts-5.10.1/bin/beam.valgrind.smp)
> ==59400==
> ==59400== ERROR SUMMARY: 460 errors from 15 contexts (suppressed: 0 from
> 0)
> How can I distinguish between these falsy reported numbers and the real
> ones?

Isn't the information you require in the return
address/function/executable reported even if this needs a little
post-processing ?

> Finally, is there any other way than Valgrind?

Yes by instrumenting your code.

Jon





More information about the erlang-questions mailing list