MySQL Bugs: #42409: Backup: valgrind warnings when making a compressed backup

Bug #42409	Backup: valgrind warnings when making a compressed backup
Submitted:	28 Jan 2009 10:30	Modified:	23 Feb 2009 14:06
Reporter:	Guilhem Bichot	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S3 (Non-critical)
Version:	6.0-bzr	OS:	Linux
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I'm using 6.0-main from yesterday (revision-id:horst@mysql.com-20090121133202-2ygkbxoxkuvkcmgb)
(BUILD/compile-pentium-valgrind-max)
./mtr --mem --valgrind --mysqld=--default-storage-engine=innodb backup_compression
produces in master.err:
090128 13:28:40 [Note] Backup: Starting backup process
090128 13:28:42 [Note] Backup: Backing up 1 database(s) `db1`
==9014== Thread 22:
==9014== Conditional jump or move depends on uninitialised value(s)
==9014==    at 0x8971149: longest_match (deflate.c:1121)
==9014==    by 0x89721CC: deflate_slow (deflate.c:1595)
==9014==    by 0x8970702: deflate (deflate.c:790)
==9014==    by 0x8A229B9: backup::Output_stream::close() (stream.cc:431)
==9014==    by 0x8A0F6A9: Backup_restore_ctx::close() (kernel.cc:956)
==9014==    by 0x8A11570: execute_backup_command(THD*, LEX*, String*, bool) (kernel.cc:244)
==9014==    by 0x8328FBD: mysql_execute_command(THD*) (sql_parse.cc:2338)
==9014==    by 0x8330E28: mysql_parse(THD*, char const*, unsigned, char const**) (sql_parse.cc:5735)
==9014==    by 0x8331DBD: dispatch_command(enum_server_command, THD*, char*, unsigned) (sql_parse.cc:1008)
==9014==    by 0x8333098: do_command(THD*) (sql_parse.cc:691)

How to repeat:
./mtr --mem --valgrind --mysqld=--default-storage-engine=innodb backup_compression

This is a duplicate of Bug#36989 - the issue is internal to the zlib library.
We should wait for resolution of the bug (e.g. valgrind suppression rule) and then close
this one.