Commit c27566ae authored by Alfranio Correia's avatar Alfranio Correia

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.
parent d2f2edbb
...@@ -9250,7 +9250,7 @@ Incident_log_event::Incident_log_event(const char *buf, uint event_len, ...@@ -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 // If the incident is not recognized, this binlog event is
// invalid. If we set incident_number to INCIDENT_NONE, the // invalid. If we set incident_number to INCIDENT_NONE, the
// invalidity will be detected by is_valid(). // invalidity will be detected by is_valid().
incident_number= INCIDENT_NONE; m_incident= INCIDENT_NONE;
DBUG_VOID_RETURN; DBUG_VOID_RETURN;
} }
m_incident= static_cast<Incident>(incident_number); m_incident= static_cast<Incident>(incident_number);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment