I have a binary that is statically linked and sometimes I like to run it under Valgrind. The suppressions for glibc in /usr/lib/valgrind/default.supp do not work in this case because they're targeted with "obj:" lines but, due to the static linking, the functions do not occur in the files specified. This is easy enough to rectify by copying the suppressions into a custom suppressions file and changing or removing the "obj:" qualifiers appropriately.
Or rather, that's how it goes for glibc-2.3. I recently upgraded to glibc-2.5 and now virtually all glibc functions generate an error (usually a conditional/jump on undefined value). I've scanned over some of the glibc code in hopes of seeing something easy for me to fix--like accessing an uninitialized global that I could tell Valgrind is defined by using the VALGRIND_MAKE_MEM_DEFINED macro--but I have not spotted any commonalities yet. It is undesirable to add a suppression for all glibc functions not only because it would be a pain but because it would, of course, reduce the efficacy of Valgrind by eliminating its ability to catch errors caused by passing bad values into glibc functions. Any advice (except "don't statically link," "downgrade glibc," etc) is most appreciated. ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
