summaryrefslogtreecommitdiff
path: root/mysql-test/valgrind.supp
diff options
context:
space:
mode:
authorunknown <rafal@quant.(none)>2007-02-08 15:57:28 +0100
committerunknown <rafal@quant.(none)>2007-02-08 15:57:28 +0100
commit33f24f2c58b97397c872616b1d5bf692dffa86fd (patch)
tree33f3fce40c8a9f4a5d2af2f016baafd7ca6f63c8 /mysql-test/valgrind.supp
parentf40fe807607fa2eef587b878903516137b02f2a6 (diff)
downloadmariadb-git-33f24f2c58b97397c872616b1d5bf692dffa86fd.tar.gz
BUG#25463 (Memory allocation problems in replication slave thread):
The problem is (most probably) caused by whole server shutting down before a slave thread terminates correctly. Fixing this requires fixing server shutdown code which has been done in 5.1 tree. Thus we ignore the issue in 5.0 assuming that it is fixed in 5.1. mysql-test/valgrind.supp: Added a suppresion rule.
Diffstat (limited to 'mysql-test/valgrind.supp')
-rw-r--r--mysql-test/valgrind.supp17
1 files changed, 17 insertions, 0 deletions
diff --git a/mysql-test/valgrind.supp b/mysql-test/valgrind.supp
index f7eb9baa4c7..e71f4541cfd 100644
--- a/mysql-test/valgrind.supp
+++ b/mysql-test/valgrind.supp
@@ -346,3 +346,20 @@
fun:_ZN19TransporterRegistry11performSendEv
fun:_ZN19TransporterRegistry14forceSendCheckEi
}
+
+#
+# BUG#25463: Probable cause - slave thread doesn't have time to terminate properly
+# because rest of the server shuts down before that. The server shutdown code has
+# been fixed in 5.1 and there this leak should not happen. Suppression has been
+# approved by Monty.
+#
+# Important: do not propagate this rule to 5.1 tree!
+#
+
+{
+ Slave thread shutdown (BUG#25463)
+ Memcheck:Leak
+ fun:calloc
+ fun:my_thread_init
+ fun:handle_slave_io
+}