Hi, * Ankur Tyagi <[email protected]> [150813 06:25]: > I am using Valgrind coming from yocto on my AM335x-EVM kit.
> But when I try to use valgrind, it doesn't give me stack trace. Following > is what I get : I actually got the same question from a customer (on an older TI arm core) earlier this summer. So luckily I rember what the fix was... > ==1732== HEAP SUMMARY: > ==1732== in use at exit: 4 bytes in 1 blocks > ==1732== total heap usage: 2 allocs, 1 frees, 8 bytes allocated > ==1732== > ==1732== 4 bytes in 1 blocks are definitely lost in loss record 1 of 1 > ==1732== at 0x4811FE8: malloc (in > /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so) To get better backtraces than this (which is useless), all you need to do is to install the debug symbols for vgpreload_memcheck-arm-linux.so. As the complete valgrind-dbg package in Yocto is far too big, I just created a new package with the debug symbols for vgpreload_memcheck-arm-linux.so. After installing this to our image (or just manually copying the debug info for that file into the rootfs), the memcheck tool from valgrind will start giving you usefull backtraces and thus, a usefull grouping of memory leaks. Cheers, Anders -- Anders Darander ChargeStorm AB / eStorm AB _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
