[Valgrind-users] 32bit app on 64bit os generates lots of system related output

[Beaman, T. <Tho...@xe...>]

Hi,

I have 64bit and 32bit apps running on my 64bit ppc64 linux 4.1 OS

uname -a
Linux  4.1.30-rt34-yocto2.2.1_standard+ #1 SMP PREEMPT Wed Jul 5 04:17:14 EDT 2017 ppc64 GNU/Linux

When I run valgrind on a 64bit app it appears to work ok.


When I switch to running valgrind on a 32bit app I get lots of system related messages (ld-2.24.so, libc-2.24.so, pthread-2.24.so ... etc) like these
# export VALGRIND_LIB=/usr/lib/valgrind

==14722== Use of uninitialised value of size 4
==14722==    at 0x4004A98: ??? (in /lib/ld-2.24.so)

==14722== Use of uninitialised value of size 4
==14722==    at 0xFA2F78C: clock_gettime (in /lib/libc-2.24.so)

==14722== Use of uninitialised value of size 4
==14722==    at 0xFEC2A18: ??? (in /lib/libpthread-2.24.so)


I saw this on valgrind 3.12.0 and upgraded to 3.13.0 and see the same thing.
# valgrind --version
valgrind-3.13.0

I have both 64bit and 32bit versions installed
# ls /usr/lib64/valgrind/mem*
/usr/lib64/valgrind/memcheck-ppc64be-linux

# ls /usr/lib/valgrind/mem*
/usr/lib/valgrind/memcheck-ppc32-linux

As a test I have tried just installing 32bit valgrind and I get the same results.

What am I missing to get my 32bit app not to print 100's of these messages ? What other useful info can I provide ?

Thanks,
Tom