From 30f4b2de5f095beeb8a6c557bb72d5012a3666e3 Mon Sep 17 00:00:00 2001
From: Soonho Kong <soonhok@cs.cmu.edu>
Date: Sat, 14 Sep 2013 19:33:47 -0700
Subject: [PATCH] Update memcheck.supp

[skip ci]
---
 src/memcheck.supp | 33 ++++++++++++++++++++++++++++++---
 1 file changed, 30 insertions(+), 3 deletions(-)

diff --git a/src/memcheck.supp b/src/memcheck.supp
index 176753894..1ebeae010 100644
--- a/src/memcheck.supp
+++ b/src/memcheck.supp
@@ -4,8 +4,7 @@
    # This warning is due to a memory-leak bug in the g++ compiler.
    # Soonho reported the problem. Gcc team said this a known problem, and will be fixed
    # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58142
-
-   Suppress_GCC-4.8_Memory_Leak_Bug_in_Thread
+   Suppress_GCC-4.8_Memory_Leak_Bug_in_Thread1
    Memcheck:Leak
    fun:*nothrow_t
    fun:*_thread_atexit
@@ -19,6 +18,35 @@
    fun:clone
 }
 
+{
+   # This warning is due to a memory-leak bug in the g++ compiler.
+   # Soonho reported the problem. Gcc team said this a known problem, and will be fixed
+   # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58142
+   Suppress_GCC-4.8_Memory_Leak_Bug_in_Thread2
+   Memcheck:Leak
+   fun:*nothrow_t
+   fun:*_thread_atexit
+   fun:*
+   obj:*/libstdc++.so*
+   fun:start_thread
+   fun:clone
+}
+
+{
+   # This warning is due to a memory-leak bug in the g++ compiler.
+   # Soonho reported the problem. Gcc team said this a known problem, and will be fixed
+   # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58142
+   Suppress_GCC-4.8_Memory_Leak_Bug_in_Thread3
+   Memcheck:Leak
+   fun:*nothrow_t
+   fun:*_thread_atexit
+   fun:*
+   fun:*_Bind_simple*
+   obj:/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18
+   fun:start_thread
+   fun:clone
+}
+
 {
    Suppress_Bash_Memory_Leak_on_Fedora19
    Memcheck:Leak
@@ -31,4 +59,3 @@
    fun:reader_loop
    fun:main
 }
-