Bug #12843 | fulltext_order_by test fails | ||
---|---|---|---|
Submitted: | 26 Aug 2005 20:01 | Modified: | 12 Jan 2006 9:08 |
Reporter: | Patrick Galbraith | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.12-beta | OS: | MacOS (OSX Darwin Kernel Version 8.2.0/Linux) |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
[26 Aug 2005 20:01]
Patrick Galbraith
[27 Aug 2005 1:56]
MySQL Verification Team
It fails on Linux Suse Pro 9.3 also: miguel@hegel:~/dbs/mysql-5.0/mysql-test> ./mysql-test-run fulltext_order_by Installing Test Databases <cut> Starting Tests TEST RESULT ------------------------------------------------------- fulltext_order_by [ fail ] Errors are (from /home/miguel/dbs/mysql-5.0/mysql-test/var/log/mysqltest-time) : mysqltest returned unexpected code 139, it has probably crashed (the last lines may be the most important ones)
[10 Sep 2005 20:20]
Sergey Petrunya
I get this warning on 4.1 compiled with valgrind: CURRENT_TEST: fulltext_order_by ==32563== ==32563== Thread 15: ==32563== Invalid write of size 1 ==32563== at 0x8140714: Item_func_match::cleanup() (item_func.h:1062) ==32563== by 0x81B5741: Item::delete_self() (item.h:327) ==32563== by 0x81A9AED: free_items(Item*) (sql_parse.cc:1181) ==32563== by 0x818861B: THD::end_statement() (sql_class.cc:1528) ==32563== by 0x81B1E60: mysql_parse(THD*, char*, unsigned) (sql_parse.cc:4317) ==32563== by 0x81AA78B: dispatch_command(enum_server_command, THD*, char*, unsigned) (sql_parse.cc:1495) ==32563== by 0x81AA05F: do_command(THD*) (sql_parse.cc:1308) ==32563== by 0x81A9439: handle_one_connection (sql_parse.cc:1040) ==32563== by 0x1BA7BAF4: thread_wrapper (vg_libpthread.c:867) ==32563== by 0xB000F5D3: do__quit (vg_scheduler.c:1867) ==32563== Address 0x1D3D4FCD is 317 bytes inside a block of size 1720 free'd ==32563== at 0x1B906114: free (vg_replace_malloc.c:153) ==32563== by 0x85213BF: my_no_flags_free (my_malloc.c:60) ==32563== by 0x81E5C18: free_tmp_table(THD*, st_table*) (sql_select.cc:5735) ==32563== by 0x82A0A32: st_select_lex_unit::cleanup() (sql_union.cc:593) ==32563== by 0x829ED4B: mysql_union(THD*, st_lex*, select_result*, st_select_lex_unit*) (sql_union.cc:34) ==32563== by 0x81D5FB6: handle_select(THD*, st_lex*, select_result*) (sql_select.cc:177) ==32563== by 0x81AC1A2: mysql_execute_command(THD*) (sql_parse.cc:2108) ==32563== by 0x81B1DF4: mysql_parse(THD*, char*, unsigned) (sql_parse.cc:4305) ==32563== by 0x81AA78B: dispatch_command(enum_server_command, THD*, char*, unsigned) (sql_parse.cc:1495) ==32563== by 0x81AA05F: do_command(THD*) (sql_parse.cc:1308) ==32563== by 0x81A9439: handle_one_connection (sql_parse.cc:1040) ==32563== by 0x1BA7BAF4: thread_wrapper (vg_libpthread.c:867) ==32563== by 0xB000F5D3: do__quit (vg_scheduler.c:1867)
[12 Jan 2006 9:08]
Sergey Vojtovich
Wasn't able to repeat both fulltext_order_by test failure and Invalid write reported by valgrind using recent 5.0.19 tree.