MySQL Bugs: #46756: Test group_min_max fails in valgrind mode

Bug #46756	Test group_min_max fails in valgrind mode
Submitted:	17 Aug 2009 9:21	Modified:	23 Oct 2009 11:51
Reporter:	Sveta Smirnova	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0, 5.1, 5.4.4 bzr	OS:	Linux
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Test group_min_max fails in valgrind.

How to repeat:
$./mtr --valgrind group_min_max
...
main.group_min_max                       [ fail ]  Found warnings/errors in server log file!
        Test ended at 2009-08-17 11:19:32
mysqltest: Logging to ''.
mysqltest: Results saved in ''.
mysqltest: Connecting to server localhost:13000 (socket /users/ssmirnova/blade12/src/mysql-azalea/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/check-warnings.test' ...
file_name       line
/users/ssmirnova/blade12/src/mysql-azalea/mysql-test/var/log/mysqld.1.err       ==22721==    at 0x3429E0D708: (within /lib64/libpthread-2.5.so)
/users/ssmirnova/blade12/src/mysql-azalea/mysql-test/var/log/mysqld.1.err       ==22721==    at 0x4A075EE: malloc (vg_replace_malloc.c:207)
...
$vim var/log/mysqld.1.err
...
==22721== Thread 3:
==22721== Syscall param pwrite64(buf) points to uninitialised byte(s)
==22721==    at 0x3429E0D708: (within /lib64/libpthread-2.5.so)
==22721==    by 0xB201B5: my_pwrite (my_pread.c:162)
==22721==    by 0xB213D9: key_cache_pwrite (mf_keycache.c:803)
==22721==    by 0xB2645F: flush_cached_blocks (mf_keycache.c:3554)
==22721==    by 0xB26B3C: flush_key_blocks_int (mf_keycache.c:3850)
==22721==    by 0xB270A3: flush_key_blocks (mf_keycache.c:4107)
==22721==    by 0xA4A20F: mi_lock_database (mi_locking.c:74)
==22721==    by 0xA32061: ha_myisam::external_lock(THD*, int) (ha_myisam.cc:1817)
==22721==    by 0x829624: handler::ha_external_lock(THD*, int) (handler.cc:5475)
==22721==    by 0x6B7AA4: unlock_external(THD*, TABLE**, unsigned int) (lock.cc:822)
==22721==    by 0x6B6C89: mysql_unlock_tables(THD*, st_mysql_lock*) (lock.cc:437)
==22721==    by 0x724A26: close_thread_tables(THD*, bool) (sql_base.cc:1466)
==22721==    by 0x6CF7AB: dispatch_command(enum_server_command, THD*, char*, unsigned int) (sql_parse.cc:1411)
==22721==    by 0x6CD869: do_command(THD*) (sql_parse.cc:743)
==22721==    by 0x6CC035: handle_one_connection (sql_connect.cc:1158)
==22721==    by 0x3429E061B4: start_thread (in /lib64/libpthread-2.5.so)
==22721==  Address 0x533f850 is 20,648 bytes inside a block of size 850,988 alloc'd
==22721==    at 0x4A075EE: malloc (vg_replace_malloc.c:207)
==22721==    by 0xB2DB67: _mymalloc (safemalloc.c:147)
==22721==    by 0xB49C30: my_large_malloc (my_largepage.c:64)
==22721==    by 0xB2095C: init_key_cache (mf_keycache.c:439)
==22721==    by 0x825A95: ha_init_key_cache (handler.cc:3678)
==22721==    by 0x6E8430: process_key_caches(int (*)(char const*, st_key_cache*)) (set_var.cc:4820)
==22721==    by 0x6C1C6A: init_server_components() (mysqld.cc:4120)
==22721==    by 0x6C27CC: main (mysqld.cc:4634)
~

Could not reproduce it on mysql-{5.0,5.1}-bugteam, mysql-pe and mysql-next using BUILD/compile-pentium-valgrind-max && (cd mysql-test; ./mtr --valgrind group_min_max).

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Still repeatable for me on blade12 using BUILD/compile/pentium64-debug-max and running as "./mtr --valgrind group_min_max"

$valgrind --version
valgrind-3.4.1