Bug #58914 Valgrind warning in rpl_make_log_name()

• Submitted: 14 Dec 2010 9:57
• Modified: 6 Jan 2011 4:58
• Reporter: Alexander Nozdrin
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S1 (Critical)
• Version: 5.6
• OS: Any
• Assigned to: Mats Kindahl
• CPU Architecture: Any

[14 Dec 2010 9:57] Alexander Nozdrin

Description:
Several tests (rpl.rpl_change_master in particular) produces
the following warning being run under valgrind 3.5.0:

==9440== 156 bytes in 1 blocks are still reachable in loss record 83 of 127
==9440==    at 0x4C20E1C: malloc (vg_replace_malloc.c:195)
==9440==    by 0x5981521: strdup (in /lib64/libc-2.5.so)
==9440==    by 0x54C64F: rpl_make_log_name(char const*, char const*, char const*) (mysqld.cc:3106)
==9440==    by 0x552952: init_server_components() (mysqld.cc:4091)
==9440==    by 0x55428F: mysqld_main(int, char**) (mysqld.cc:4670)
==9440==    by 0x547A62: main (main.cc:24)

How to repeat:
Log: http://pb2.norway.sun.com/web.py?action=archive_download&archive_id=2662212&pretty=please

Firstly noticed in the 'tor.didriksen@or... 2010-12-13 21:06:48' build
in daily-trunk-bugfixing.

[14 Dec 2010 21:55] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/126850

3427 Mats Kindahl	2010-12-14
      Bug #58914: Valgrind warning in rpl_make_log_name()
      
      Adding calls to my_free to free the memory allocated for:
      - log_bin_basename
      - log_bin_index
      - relay_log_basename
      - relay_log_index

[17 Dec 2010 12:56] Bugs System

Pushed into mysql-trunk 5.6.1 (revid:[e-mail]-20101217125013-y8pb3az32rtbplc9) (version source revid:[e-mail]-20101214215441-o3vsxdg3eowg0ix5) (merge vers: 5.6.1) (pib:24)

[6 Jan 2011 4:58] Jon Stephens

Does not appear in a release; no changelog entry needed. Closed.