Bug #12505 mysql server crashes during execution of innodb_view test from funcs_1 suite
Submitted: 10 Aug 2005 18:25 Modified: 21 Aug 2005 17:23
Reporter: Alexey Stroganov Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:the latest 5.0.12pre OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[10 Aug 2005 18:25] Alexey Stroganov
Description:
Running innodb_views test from funcs_1 test suite  in multithread environment(stress test) for some time (less than 1 min) will lead to crash:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1121237936 (LWP 23405)]
0x08211cdc in mysql_update (thd=0x429c2660, table_list=0x8d595a8, fields=@0x429c2910, values=@0x429c2ac8, conds=0x8d59900, order_num=0, order=0x0, limit=18446744073709551615, handle_duplicates=DUP_ERROR, ignore=false) at sql_update.cc:162
162       table->file->info(HA_STATUS_VARIABLE | HA_STATUS_NO_LOCK);

(gdb) bt
#0  0x08211cdc in mysql_update (thd=0x429c2660, table_list=0x8d595a8, fields=@0x429c2910,
    values=@0x429c2ac8, conds=0x8d59900, order_num=0, order=0x0, limit=18446744073709551615,
    handle_duplicates=DUP_ERROR, ignore=false) at sql_update.cc:162
#1  0x081aa158 in mysql_execute_command (thd=0x429c2660) at sql_parse.cc:3178
#2  0x081b08db in mysql_parse (thd=0x429c2660,
    inBuf=0x8d59518 "UPDATE test.v2 SET F59 = 9879 where f59 = 919", length=45)
    at sql_parse.cc:5393
#3  0x081a603e in dispatch_command (command=COM_QUERY, thd=0x429c2660,
    packet=0x429e6271 "UPDATE test.v2 SET F59 = 9879 where f59 = 919 ", packet_length=47)
    at sql_parse.cc:1660
#4  0x081a5826 in do_command (thd=0x429c2660) at sql_parse.cc:1460
#5  0x081a492c in handle_one_connection (arg=0x429c2660) at sql_parse.cc:1113
#6  0x40049aa7 in start_thread () from /lib/tls/libpthread.so.0
#7  0x4017ac2e in clone () from /lib/tls/libc.so.6

How to repeat:
Run stress test with test case above.

Until stress test will be integrated to regular mysql-test suite please contact
me and I will provide all necessary information.
[21 Aug 2005 17:23] Alexey Stroganov
Further investgation shows that this issue could be repeated with more simple test case, see BUG#12569.