summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorandrelkin <andrei.elkin@mariadb.com>2017-07-06 14:03:23 +0300
committerandrelkin <andrei.elkin@mariadb.com>2017-09-04 18:54:03 +0300
commit8592ff9e8d477ccea322fb952266cb0f18e6c3b7 (patch)
tree4339aead4e04f33bf2c05387922f2ae58e9bb5b1
parent720928782faee2f5ca576a2a3bc2bead001c6369 (diff)
downloadmariadb-git-8592ff9e8d477ccea322fb952266cb0f18e6c3b7.tar.gz
MDEV-12731
Was reported as 'rpl.rpl_gtid_stop_start fails with Valgrind in buildbot and outside'. The 'Conditional jump or move depends on uninitialized value' valgrind complaint is valid and means THD::m_current_stage_key that is not initialized indeed by constructor. Fixed with its initialization added to the initializer list of THD::THD. Double checked with mysql to have found a similar fixes for the very same issue which was discovered after P_S merge to Maria (60589aeee where the member is introduced) had been done.
-rw-r--r--sql/sql_class.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/sql/sql_class.cc b/sql/sql_class.cc
index 003a4019017..9aedba3c426 100644
--- a/sql/sql_class.cc
+++ b/sql/sql_class.cc
@@ -698,6 +698,7 @@ THD::THD(my_thread_id id, bool is_wsrep_applier)
/* statement id */ 0),
rli_fake(0), rgi_fake(0), rgi_slave(NULL),
protocol_text(this), protocol_binary(this),
+ m_current_stage_key(0),
in_sub_stmt(0), log_all_errors(0),
binlog_unsafe_warning_flags(0),
binlog_table_maps(0),