Hi,
We have several DM814x and DM816x projects, for a few years now. Per the EZSDK, we use Sourcery G++ Lite 2009q1-203. Our rootfs is fairly up to date with regards to security updates like openssl-1.0.2g, etc., thanks to buildroot. However, we are having a lot of problems running valgrind on the target. I've tried with old versions of valgrind up to the latest valgrind-3.11.0, but I keep getting hundreds to thousands of errors from even very simple programs, and reports of zero allocations in programs that we know have malloc calls. Example:
==31636== Memcheck, a memory error detector
==31636== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==31636== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==31636==
==31636== Conditional jump or move depends on uninitialised value(s)
==31636== at 0x40160B8: ??? (in /lib/ld-2.8.so)
==31636==
.
. <hundreds of similar errors>
.
==31636== Use of uninitialised value of size 4
==31636== at 0x400E7EC: ??? (in /lib/ld-2.8.so)
==31636==
==31636==
==31636== HEAP SUMMARY:
==31636== in use at exit: 0 bytes in 0 blocks
==31636== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==31636==
==31636== All heap blocks were freed -- no leaks are possible
==31636==
==31636== For counts of detected and suppressed errors, rerun with: -v
==31636== Use --track-origins=yes to see where uninitialised values come from
==31636== ERROR SUMMARY: 32712 errors from 295 contexts (suppressed: 0 from 0)
So my question is: is there a known version of valgrind that works with the DM81xx and this antiquated toolchain?
Thanks,
Dan -
