> I installed Valgrind on my openWRT, ARMV7 machine, ... > 1. Valgrind version is 3.10.1 > 2. OpenWRT version is Barrier Breaker, linux distribution
> **************** > root@OpenWrt:/# valgrind --leak-check=yes --workaround-gcc296-bugs=yes > ./usr/bin/cm > ==1514== Memcheck, a memory error detector > ==1514== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==1514== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info > ==1514== Command: ./usr/bin/cm > ==1514== > ==1514== Conditional jump or move depends on uninitialised value(s) > ==1514== at 0x49DF018: ??? (in /lib/libuClibc-0.9.33.2.so > <http://libuClibc-0.9.33.2.so>) Please try my other suggestion (from a previous response): > Add the command-line parameter "--vgdb-error=0" > to the invocation of valgrind. Open another terminal window > and follow the directions on running gdb. When valgrind's complaint > appears, then get more information from gdb: > (gdb) bt # backtrace of subroutine calls > (gdb) info reg # register contents > (gdb) x/8i $pc-4*4 # instruction stream In particular, the "info reg" may tell us that the assembly language code (whether generated by compiler or a human) is referencing memory on the wrong side of the stack pointer. The "--workaround-gcc296-bugs=yes" tells valgrind(memcheck) not to complain about the *memory access* itself (neither read nor write), but any *value fetched* is of course uninitialized: even a preceding store could have been clobbered by a signal handler. I suspect that is the cause of the message quoted above. Did you say earlier that similar complaints were reported regardless of which application is being checked by memcheck? Do the complaints appear when checking /bin/date ? If so, then it may be reasonable to suppress those complaints; read the documentation! [And if gcc-2.96 really *is* the version that compiled libuClibc-0.9.33.2.so then you should complain to the distributor for causing such pain to developers. Suggest a cross-compiler running on x86_64 using a recent version of gcc or clang. -- ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
