List:Commits« Previous MessageNext Message »
From:Luis Soares Date:September 21 2010 11:32am
Subject:bzr commit into mysql-next-mr-bugfixing branch (luis.soares:3298) Bug#56882
View as plain text  
#At file:///home/lsoares/Workspace/bzr/work/bugfixing/56882/mysql-next-mr-bugfixing-push/ based on revid:tor.didriksen@stripped

 3298 Luis Soares	2010-09-21
      BUG#56882: binlog_base64_flag fails on valgrind and win debug 
                 max platforms
      In some cases, the variable err in mysql_client_binlog_statement
      would not be initialized but still some conditional jumps would
      rely on its value. This is for instance the case when a BINLOG
      event is truncated and it returns an error. In this case the
      'err' variable is not initialized at that time, but we jump to
      the label 'end' and then check the following condition: 
         if ((error || err) && ... )
      This makes valgrind complain that there is a conditional jump or
      move depending on an uninitialized value.
      We fix this by initializing the variable err to 0.

=== modified file 'sql/'
--- a/sql/	2010-09-01 02:51:08 +0000
+++ b/sql/	2010-09-21 11:32:50 +0000
@@ -147,7 +147,7 @@ void mysql_client_binlog_statement(THD* 
-  int err;
+  int err= 0;
   Relay_log_info *rli;
   rli= thd->rli_fake;
   if (!rli && (rli= thd->rli_fake= new Relay_log_info(FALSE)))
@@ -264,8 +264,6 @@ void mysql_client_binlog_statement(THD* 
 #if !defined(MYSQL_CLIENT) && defined(HAVE_REPLICATION)
       err= ev->apply_event(rli);
-      err= 0;
         Format_description_log_event should not be deleted because it

Attachment: [text/bzr-bundle] bzr/
bzr commit into mysql-next-mr-bugfixing branch (luis.soares:3298) Bug#56882Luis Soares21 Sep