Hi John, Thank you for all the useful advice.
My first test was to just run on a simple 32bit hello world file, and it generated the same type of warnings. I had previously checked the 64bit and 32bit default.supp files existed and were identical. But from your ideas, I did notice that the errors I am getting did not fall under any of the rules in the default.supp file. Another source on suppression files (https://wiki.wxwidgets.org/Valgrind_Suppression_File_Howto ) lead me to do this. valgrind --gen-suppressions=all --log-file=min.log and running this file through the grindmerge script, I was able to add a number of new rules. This allowed my helloworld file to run without warnings, and now I will go back to testing with my application. Thank you for all your help on this, Tom >> 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 > [[snip]] >> 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 ? > 1) Check the default suppressions file; something like > /usr/lib*/valgrind/default.supp ("strace -o strace.out -e trace=file valgrind > /bin/date" to find the exact names). > Make sure it has suppressions for ld-2.24 like on x86_64, such as: > { > dl-hack3-cond-1 > Memcheck:Cond > obj:*/lib*/ld-2.24*.so* > obj:*/lib*/ld-2.24*.so* > obj:*/lib*/ld-2.24*.so* > } ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
