From e0526914b6acb91f8cf15bd536ad40e226158d1b Mon Sep 17 00:00:00 2001 From: Alfranio Correia Date: Tue, 21 Apr 2009 15:31:21 +0100 Subject: [PATCH] BUG#44378 rpl_binlog_corruption fails with warning messages in Valgrind The rpl_binlog_corruption test case was inject failures, specifically, incidents with invalid numbers to see if the replication was failing gracefully. However, this test was causing the following warning message in Valgrind: "Conditional jump or move depends on uninitialised value(s)" The patch fixes the problem by correctly initializing the m_inicident number. --- sql/log_event.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql/log_event.cc b/sql/log_event.cc index 917e79b86f2..a10a36f3b43 100644 --- a/sql/log_event.cc +++ b/sql/log_event.cc @@ -9250,7 +9250,7 @@ Incident_log_event::Incident_log_event(const char *buf, uint event_len, // If the incident is not recognized, this binlog event is // invalid. If we set incident_number to INCIDENT_NONE, the // invalidity will be detected by is_valid(). - incident_number= INCIDENT_NONE; + m_incident= INCIDENT_NONE; DBUG_VOID_RETURN; } m_incident= static_cast(incident_number);