Bug #48096 Valgrind - get_next_partition_id_list(st_partition_iter*) sql_partition.cc:7319
Submitted: 15 Oct 2009 19:26 Modified: 27 Oct 2009 23:08
Reporter: Patrick Crews Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.5 WL#3352 OS:Any
Assigned to: Mikael Ronström CPU Architecture:Any
Tags: partitioning, uninitialized value, valgrind
Triage: Triaged: D2 (Serious)

[15 Oct 2009 19:26] Patrick Crews
Valgrind warning when running the RQG's partition pruning grammar:
==15631== Conditional jump or move depends on uninitialised value(s)
==15631==    at 0x81DC195: get_next_partition_id_list(st_partition_iter*) (sql_partition.cc:7319)
==15631==    by 0x87A7EAB: find_used_partitions(st_part_prune_param*, SEL_ARG*) (opt_range.cc:3440)
==15631==    by 0x87A9281: prune_partitions(THD*, st_table*, Item*) (opt_range.cc:2771)
==15631==    by 0x8615E5B: JOIN::optimize() (sql_select.cc:881)
==15631==    by 0x862078A: mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*) (sql_select.cc:2387)
==15631==    by 0x862F2C6: handle_select(THD*, st_lex*, select_result*, unsigned long) (sql_select.cc:270)
==15631==    by 0x849047E: mysql_execute_command(THD*) (sql_parse.cc:3247)
==15631==    by 0x84A4E86: mysql_parse(THD*, char const*, unsigned int, char const**) (sql_parse.cc:6002)
==15631==    by 0x84A762B: dispatch_command(enum_server_command, THD*, char*, unsigned int) (sql_parse.cc:1222)
==15631==    by 0x84AB280: do_command(THD*) (sql_parse.cc:855)
==15631==    by 0x846FF06: handle_one_connection (sql_connect.cc:1131)
==15631==    by 0x403F4FE: start_thread (in /lib/tls/i686/cmov/libpthread-2.9.so)
==15631==    by 0x41AC49D: clone (in /lib/tls/i686/cmov/libc-2.9.so)

How to repeat:
Use the RQG:
perl ./runall.pl --basedir=<path>/mysql-5.4 --gendata=conf/partition_pruning.zz
--threads=1 --valgrind --Validator=MarkErrorLog --queries=10000

The error log will have the querues as well as the output present.
[27 Oct 2009 23:08] Patrick Crews
Unable to repeat this bug with the latest version of the tree.