mysqld crashes by issuing select sum()

MariaDB [frr]>  create table t2 (c1 bigint) ;

Query OK, 0 rows affected (0.10 sec)

MariaDB [frr]>  insert into t2  values (9223372036854775807), (9223372036854775807) ;

Query OK, 2 rows affected (0.02 sec)

Records: 2  Duplicates: 0  Warnings: 0

MariaDB [frr]>  select sum(c1) from t2;

ERROR 2006 (HY000): MySQL server has gone away

No connection. Trying to reconnect...

Aug 23 12:23:24 t4w5 mysqld: 2018-08-23 12:23:24 0x7f29d5ffb700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.17/storage/innobase/trx/trx0undo.cc line 1516

Aug 23 12:23:24 t4w5 mysqld: InnoDB: Failing assertion: mach_read_from_2(undo_page + TRX_UNDO_PAGE_HDR + TRX_UNDO_PAGE_TYPE) == TRX_UNDO_UPDATE

Aug 23 12:23:24 t4w5 mysqld: InnoDB: We intentionally generate a memory trap.

Aug 23 12:23:24 t4w5 mysqld: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

Aug 23 12:23:24 t4w5 mysqld: InnoDB: If you get repeated assertion failures or crashes, even

Aug 23 12:23:24 t4w5 mysqld: InnoDB: immediately after the mysqld startup, there may be

Aug 23 12:23:24 t4w5 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to

Aug 23 12:23:24 t4w5 mysqld: InnoDB: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/

Aug 23 12:23:24 t4w5 mysqld: InnoDB: about forcing recovery.

Aug 23 12:23:24 t4w5 mysqld: 180823 12:23:24 [ERROR] mysqld got signal 6 ;

Aug 23 12:23:24 t4w5 mysqld: This could be because you hit a bug. It is also possible that this binary

Aug 23 12:23:24 t4w5 mysqld: or one of the libraries it was linked against is corrupt, improperly built,

Aug 23 12:23:24 t4w5 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

Aug 23 12:23:24 t4w5 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Aug 23 12:23:24 t4w5 mysqld: We will try our best to scrape up some info that will hopefully help

Aug 23 12:23:24 t4w5 mysqld: diagnose the problem, but since we have already crashed,

Aug 23 12:23:24 t4w5 mysqld: something is definitely wrong and this may fail.

Aug 23 12:23:24 t4w5 mysqld: Server version: 10.2.17-MariaDB

Aug 23 12:23:24 t4w5 mysqld: key_buffer_size=134217728

Aug 23 12:23:24 t4w5 mysqld: read_buffer_size=131072

Aug 23 12:23:24 t4w5 mysqld: max_used_connections=3

Aug 23 12:23:24 t4w5 mysqld: max_threads=153

Aug 23 12:23:24 t4w5 mysqld: thread_count=9

Aug 23 12:23:24 t4w5 mysqld: It is possible that mysqld could use up to

Aug 23 12:23:24 t4w5 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467246 K  bytes of memory

Aug 23 12:23:24 t4w5 mysqld: Hope that's ok; if not, decrease some variables in the equation.

Aug 23 12:23:24 t4w5 mysqld: Thread pointer: 0x0

Aug 23 12:23:24 t4w5 mysqld: Attempting backtrace. You can use the following information to find out

Aug 23 12:23:24 t4w5 mysqld: where mysqld died. If you see no messages after this, something went

Aug 23 12:23:24 t4w5 mysqld: terribly wrong...

Aug 23 12:23:24 t4w5 mysqld: stack_bottom = 0x0 thread_stack 0x49000

Aug 23 12:23:24 t4w5 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x564b6f0ce58e]

Aug 23 12:23:24 t4w5 mysqld: mysys/stacktrace.c:268(my_print_stacktrace)[0x564b6eb4c335]

Aug 23 12:23:25 t4w5 mysqld: sigaction.c:0(__restore_rt)[0x7f2a0a33e5e0]

Aug 23 12:23:25 t4w5 mysqld: :0(__GI_raise)[0x7f2a0884b1f7]

Aug 23 12:23:25 t4w5 mysqld: :0(__GI_abort)[0x7f2a0884c8e8]

Aug 23 12:23:25 t4w5 mysqld: /usr/sbin/mysqld(+0x429a88)[0x564b6e8fba88]

Aug 23 12:23:25 t4w5 mysqld: ut/ut0rbt.cc:221(rbt_tree_add_child(ib_rbt_t const*, ib_rbt_bound_t*, ib_rbt_node_t*) [clone .isra.4] [clone .part.5])[0x564b6ee8738c]

Aug 23 12:23:25 t4w5 mysqld: trx/trx0undo.cc:1503(trx_undo_assign_undo(trx_t*, trx_rseg_t*, trx_undo_t**, unsigned long))[0x564b6ee69d3c]

Aug 23 12:23:25 t4w5 mysqld: trx/trx0rec.cc:1963(trx_undo_report_row_operation(que_thr_t*, dict_index_t*, dtuple_t const*, upd_t const*, unsigned long, unsigned char const*, unsigned long const*, unsigned long*))[0x564b6eeaeae3]

Aug 23 12:23:25 t4w5 mysqld: btr/btr0cur.cc:4833(btr_cur_del_mark_set_clust_rec(buf_block_t*, unsigned char*, dict_index_t*, unsigned long const*, que_thr_t*, dtuple_t const*, mtr_t*))[0x564b6ee2e100]

Aug 23 12:23:25 t4w5 mysqld: row/row0upd.cc:2986(row_upd_clust_step(upd_node_t*, que_thr_t*))[0x564b6ee3015a]

Aug 23 12:23:25 t4w5 mysqld: row/row0upd.cc:3281(row_upd_step(que_thr_t*))[0x564b6edcaee0]

Aug 23 12:23:25 t4w5 mysqld: que/que0que.cc:1031(que_run_threads(que_thr_t*))[0x564b6edcb983]

Aug 23 12:23:25 t4w5 mysqld: que/que0que.cc:1230(que_eval_sql(pars_info_t*, char const*, unsigned long, trx_t*))[0x564b6ef2b2ec]

Aug 23 12:23:25 t4w5 mysqld: dict/dict0stats.cc:321(dict_stats_exec_sql(pars_info_t*, char const*, trx_t*))[0x564b6ef32f5f]

Aug 23 12:23:25 t4w5 mysqld: dict/dict0stats.cc:2490(dict_stats_save(dict_table_t*, unsigned long const*))[0x564b6ef34e06]

Aug 23 12:23:25 t4w5 mysqld: dict/dict0stats.cc:3203(dict_stats_update(dict_table_t*, dict_stats_upd_option_t))[0x564b6ef37043]

Aug 23 12:23:25 t4w5 mysqld: pthread_create.c:0(start_thread)[0x7f2a0a336e25]

Aug 23 12:23:25 t4w5 mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f2a0890e34d]

Aug 23 12:23:25 t4w5 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

Aug 23 12:23:25 t4w5 mysqld: information that should help you find out what is causing the crash.

Aug 23 12:23:25 t4w5 abrt-hook-ccpp: Process 14678 (mysqld) of user 996 killed by SIGABRT - dumping core

Aug 23 12:23:28 t4w5 abrt-hook-ccpp: Failed to create core_backtrace: waitpid failed: No child processes

Aug 23 12:23:28 t4w5 systemd: mariadb.service: main process exited, code=killed, status=6/ABRT

Aug 23 12:23:28 t4w5 systemd: Unit mariadb.service entered failed state.

Aug 23 12:23:28 t4w5 systemd: mariadb.service failed.

Aug 23 12:23:28 t4w5 abrt-server: Package 'MariaDB-server' isn't signed with proper key