Try to fix the MC/AsmParser/section.s failure on the llvm-x86_64-linux-vg_leak

bot. I am not sure if this is valid Valgrind exclusion file syntax, but the
Internet seems to think so.

llvm-svn: 126051

1 files changed, 4 insertions, 4 deletions

diff --git a/llvm/utils/valgrind/x86_64-pc-linux-gnu.supp b/llvm/utils/valgrind/x86_64-pc-linux-gnu.supp
index f5aae990f69..7b2dd4517da 100644
--- a/llvm/utils/valgrind/x86_64-pc-linux-gnu.supp
+++ b/llvm/utils/valgrind/x86_64-pc-linux-gnu.supp
@@ -11,19 +11,19 @@
 {
    ADDRESS_IN_RANGE/Invalid read of size 4
    Memcheck:Addr4
-   obj:/usr/bin/python2.5
+   obj:/usr/bin/python*
 }
 
 {
    ADDRESS_IN_RANGE/Invalid read of size 4
    Memcheck:Value8
-   obj:/usr/bin/python2.5
+   obj:/usr/bin/python*
 }
 
 {
    ADDRESS_IN_RANGE/Conditional jump or move depends on uninitialised value
    Memcheck:Cond
-   obj:/usr/bin/python2.5
+   obj:/usr/bin/python*
 }
 
 {
@@ -42,5 +42,5 @@
    We don't care if python leaks
    Memcheck:Leak
    fun:malloc
-   obj:/usr/bin/python2.5
+   obj:/usr/bin/python*
 }