diff options
| author | Alfranio Correia <alfranio.correia@sun.com> | 2009-04-21 15:31:21 +0100 |
|---|---|---|
| committer | Alfranio Correia <alfranio.correia@sun.com> | 2009-04-21 15:31:21 +0100 |
| commit | e0526914b6acb91f8cf15bd536ad40e226158d1b (patch) | |
| tree | d2423d6e6c8dbbb0acb408b16f4b0b4264127639 | |
| parent | 626a720387dbb15c0cc039b611ba69b56943d10d (diff) | |
| download | mariadb-git-e0526914b6acb91f8cf15bd536ad40e226158d1b.tar.gz | |
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.
| -rw-r--r-- | sql/log_event.cc | 2 |
1 files changed, 1 insertions, 1 deletions
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>(incident_number); |