Bug #86472 handle_fatal_signal (sig=6) in wrapper_to_string | sql/json_dom.cc:2123
Submitted: 26 May 2017 9:40 Modified: 11 Jul 2017 11:46
Reporter: Ramesh Sivaraman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: DML Severity:S3 (Non-critical)
Version:5.7.18 OS:Ubuntu (Xenial)
Assigned to: CPU Architecture:Any
Tags: debug

[26 May 2017 9:40] Ramesh Sivaraman
Description:
GDB info
{code}
#0  __pthread_kill (threadid=<optimized out>, signo=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:62
#1  0x000000000195d505 in my_write_core (sig=6) at /ssd/ramesh/workdir/mysql-server_dbg/mysys/stacktrace.c:249
#2  0x0000000000efeb01 in handle_fatal_signal (sig=6) at /ssd/ramesh/workdir/mysql-server_dbg/sql/signal_handler.cc:220
#3  <signal handler called>
#4  0x00007ff556f7f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#5  0x00007ff556f8102a in __GI_abort () at abort.c:89
#6  0x00000000014ce897 in wrapper_to_string (wr=..., buffer=0x7ff5594c5c50, json_quoted=true, func_name=0x1f1cd11 "?", depth=1) at /ssd/ramesh/workdir/mysql-server_dbg/sql/json_dom.cc:2123
#7  0x00000000014cea37 in Json_wrapper::to_string (this=0x7ff51a5b35d0, buffer=0x7ff5594c5c50, json_quoted=true, func_name=0x1f1cd11 "?") at /ssd/ramesh/workdir/mysql-server_dbg/sql/json_dom.cc:2146
#8  0x0000000000fb82ba in Item_cache_json::val_str (this=0x7ff51a5b3508, tmp=0x7ff5594c5c50) at /ssd/ramesh/workdir/mysql-server_dbg/sql/item.cc:9992
#9  0x00000000014a631a in Item_sum_hybrid::val_str (this=0x7ff51a5b2f10, str=0x7ff5594c5c50) at /ssd/ramesh/workdir/mysql-server_dbg/sql/item_sum.cc:2143
#10 0x0000000000fb0841 in Item::send (this=0x7ff51a5b2f10, protocol=0x7ff51a413198, buffer=0x7ff5594c5c50) at /ssd/ramesh/workdir/mysql-server_dbg/sql/item.cc:7511
#11 0x0000000001598630 in THD::send_result_set_row (this=0x7ff51a412000, row_items=0x7ff51a5b3ad8) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_class.cc:4661
#12 0x0000000001592913 in Query_result_send::send_data (this=0x7ff51a5b32f8, items=...) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_class.cc:2716
#13 0x00000000015b1695 in end_send_group (join=0x7ff51a5b3838, qep_tab=0x0, end_of_records=true) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_executor.cc:3039
#14 0x00000000015ac4ab in do_select (join=0x7ff51a5b3838) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_executor.cc:891
#15 0x00000000015aa54a in JOIN::exec (this=0x7ff51a5b3838) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_executor.cc:199
#16 0x000000000164ccec in handle_query (thd=0x7ff51a412000, lex=0x7ff51a4142f8, result=0x7ff51a5b32f8, added_options=0, removed_options=0) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_select.cc:184
#17 0x00000000015fd17b in execute_sqlcom_select (thd=0x7ff51a412000, all_tables=0x0) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_parse.cc:5196
#18 0x00000000015f6067 in mysql_execute_command (thd=0x7ff51a412000, first_level=true) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_parse.cc:2795
#19 0x00000000015fe0a5 in mysql_parse (thd=0x7ff51a412000, parser_state=0x7ff5594c7510) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_parse.cc:5612
#20 0x00000000015f2cf1 in dispatch_command (thd=0x7ff51a412000, com_data=0x7ff5594c7dc0, command=COM_QUERY) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_parse.cc:1461
#21 0x00000000015f1b3e in do_command (thd=0x7ff51a412000) at /ssd/ramesh/workdir/mysql-server_dbg/sql/sql_parse.cc:999
#22 0x0000000001734543 in handle_connection (arg=0x7ff52e3fb560) at /ssd/ramesh/workdir/mysql-server_dbg/sql/conn_handler/connection_handler_per_thread.cc:300
#23 0x0000000001db496b in pfs_spawn_thread (arg=0x7ff53f7dbb20) at /ssd/ramesh/workdir/mysql-server_dbg/storage/perfschema/pfs.cc:2188
#24 0x00007ff557bc26ba in start_thread (arg=0x7ff5594c8700) at pthread_create.c:333
#25 0x00007ff55705082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

{code}

How to repeat:
Testcase

DROP DATABASE test;
SELECT MIN(CASE 0 WHEN 1 THEN JSON_ARRAY()ELSE NULL END);
[26 May 2017 13:08] MySQL Verification Team
Thank you for the bug report, verified as described. Server version 8.0 not affected by this bug.
[11 Jul 2017 11:46] Erlend Dahl
Fixed in 8.0.1 under the heading of

Bug#22887227 	ASSERTION FAILED: THIS_TYPE != JSON_DOM::J_ERROR