- valgrind is not happy about us now processing /proc/self/auxv on Linux,
this can be used to suppress the false positives when running
rpm under valgrind. At least until a better solution is found or
valgrind is taught to treat /proc/self/auxv specially (see
https://bugs.kde.org/show_bug.cgi?id=253519)
check-buildroot check-rpaths check-rpaths-worker \
find-debuginfo.sh find-lang.sh \
perldeps.pl perl.prov perl.req pythondeps.sh osgideps.pl \
- rpmdb_loadcvt rpm.daily rpm.log rpm2cpio.sh \
+ rpmdb_loadcvt rpm.daily rpm.log rpm.supp rpm2cpio.sh \
tcl.req tgpg vpkg-provides.sh \
find-requires.php find-provides.php \
find-php-provides find-php-requires \
rpmdb_loadcvt rpm2cpio.sh tcl.req tgpg
rpmconfig_DATA = \
- rpm.daily rpm.log \
+ rpm.daily rpm.log rpm.supp \
macros.perl macros.php macros.python
--- /dev/null
+# This is a valgrind suppression file for rpm.
+# Rpm now processes /proc/self/auxv on Linux, but valgrind does not
+# like that (see https://bugs.kde.org/show_bug.cgi?id=253519). To
+# avoid the related false positives from valgrind, use this with
+# 'valgrind --suppressions=rpm.supp [...]' when using it on rpm.
+
+{
+ defaultMachine_strdup
+ Memcheck:Addr1
+ fun:__GI_strlen
+ fun:strdup
+ fun:defaultMachine
+}
+
+{
+ defaultMachine_memcpy1
+ Memcheck:Addr1
+ fun:__GI_memcpy
+ fun:defaultMachine
+}
+
+{
+ defaultMachine_memcpy2
+ Memcheck:Addr2
+ fun:__GI_memcpy
+ fun:defaultMachine
+}
+
+{
+ defaultMachine_memcpy4
+ Memcheck:Addr4
+ fun:__GI_memcpy
+ fun:defaultMachine
+}