[MDEV-4801] Server crashes in my_strdup on setting innodb_ft_user_stopword_table to DEFAULT Created: 2013-07-20  Updated: 2013-08-06  Resolved: 2013-08-06

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: 10.0.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-3932 5.6 merge Closed
relates to MDEV-4744 InnoDB Fulltext indexes Closed

 Description   

#3  <signal handler called>
#4  0x0000000000e1733e in my_strdup (from=0x0, my_flags=0) at /home/elenst/bzr/10.0-monty/mysys/my_malloc.c:236
#5  0x000000000063dab2 in update_func_str (thd=0x3162f70, var=0x15af5c0, tgt=0x7fd9e8006360, save=0x2494a50) at /home/elenst/bzr/10.0-monty/sql/sql_plugin.cc:2658
#6  0x000000000063f280 in sys_var_pluginvar::session_update (this=0x2521418, thd=0x3162f70, var=0x7fda281f2bc0) at /home/elenst/bzr/10.0-monty/sql/sql_plugin.cc:3242
#7  0x000000000058f3f9 in sys_var::update (this=0x2521418, thd=0x3162f70, var=0x7fda281f2bc0) at /home/elenst/bzr/10.0-monty/sql/set_var.cc:199
#8  0x000000000058f8fb in sys_var::set_default (this=0x2521418, thd=0x3162f70, type=OPT_SESSION) at /home/elenst/bzr/10.0-monty/sql/set_var.cc:264
#9  0x0000000000590505 in set_var::update (this=0x7fd9e8006b90, thd=0x3162f70) at /home/elenst/bzr/10.0-monty/sql/set_var.cc:667
#10 0x00000000005900c6 in sql_set_variables (thd=0x3162f70, var_list=0x3166788) at /home/elenst/bzr/10.0-monty/sql/set_var.cc:571
#11 0x0000000000629bdc in mysql_execute_command (thd=0x3162f70) at /home/elenst/bzr/10.0-monty/sql/sql_parse.cc:3611
#12 0x0000000000630e3c in mysql_parse (thd=0x3162f70, rawbuf=0x7fd9e8006a98 "SET SESSION innodb_ft_user_stopword_table=default", length=49, parser_state=0x7fda281f34e0) at /home/elenst/bzr/10.0-monty/sql/sql_parse.cc:6190
#13 0x0000000000623d7b in dispatch_command (command=COM_QUERY, thd=0x3162f70, packet=0x3168351 "SET SESSION innodb_ft_user_stopword_table=default", packet_length=49) at /home/elenst/bzr/10.0-monty/sql/sql_parse.cc:1266
#14 0x0000000000622efa in do_command (thd=0x3162f70) at /home/elenst/bzr/10.0-monty/sql/sql_parse.cc:982
#15 0x00000000007351aa in do_handle_one_connection (thd_arg=0x3162f70) at /home/elenst/bzr/10.0-monty/sql/sql_connect.cc:1379
#16 0x0000000000734b78 in handle_one_connection (arg=0x3162f70) at /home/elenst/bzr/10.0-monty/sql/sql_connect.cc:1293
#17 0x00000000009aed14 in pfs_spawn_thread (arg=0x2fc5e30) at /home/elenst/bzr/10.0-monty/storage/perfschema/pfs.cc:1853
#18 0x00007fda3ee8fe9a in start_thread (arg=0x7fda281f4700) at pthread_create.c:308
#19 0x00007fda3e183cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112

bzr version-info

revision-id: sergii@pisem.net-20130717165112-i9klgxk4enpvc09a
revno: 3637
branch-nick: 10.0-monty

Not reproducible on MySQL 5.6.10 or MySQL 5.6.12.

Test case:

--source include/have_innodb.inc
 
SET SESSION innodb_ft_user_stopword_table=default;

If using MTR, make sure you run it with --innodb-ft-default-stopword (MTR disables it by default)



 Comments   
Comment by Sergey Vojtovich [ 2013-08-06 ]

Fixed in 10.0.4.

Generated at Thu Feb 08 06:59:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.