在线添加从库配置，开启从库复制，实例直接挂了

[witty-sun]

error日志如下
2017-12-21 15:51:18 94625 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysql-bin.000015' at position 490458228
07:51:18 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=268435456
read_buffer_size=33554432
max_used_connections=1
max_threads=2001
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 131427664 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7610a10000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f8370e9e9a8 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x20)[0x8ec750]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x35f)[0x65ea1f]
/lib64/libpthread.so.0(+0xf5e0)[0x7f8370b505e0]
/usr/local/mysql/bin/mysqld(ZN12ha_federated7rnd_posEPhS0+0x2b)[0x90c13b]
/usr/local/mysql/bin/mysqld(_ZN7handler17rnd_pos_by_recordEPh+0xc2)[0x5b5282]
/usr/local/mysql/bin/mysqld(_ZN14Rows_log_event24do_index_scan_and_updateEPK14Relay_log_info+0x220)[0x882480]
/usr/local/mysql/bin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0x58a)[0x88180a]
/usr/local/mysql/bin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x58)[0x879ca8]
/usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x20e)[0x8b1bfe]
/usr/local/mysql/bin/mysqld(handle_slave_sql+0x134a)[0x8b50ca]
/lib64/libpthread.so.0(+0x7e25)[0x7f8370b48e25]
/lib64/libc.so.6(clone+0x6d)[0x7f836fc1b34d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 3
Status: NOT_KILLED

The manual page at http:https://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
171221 15:51:18 mysqld_safe Number of processes running now: 0
171221 15:51:18 mysqld_safe mysqld restarted
2017-12-21 15:51:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-12-21 15:51:18 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.32-log) starting as process 95069 ...
2017-12-21 15:51:18 95069 [Warning] Although a path was specified for the --slow-query-log-file option, log tables are used. To enable logging to files use the --log-output=file option.
2017-12-21 15:51:18 95069 [Warning] Using unique option prefix innodb_read_ahead instead of innodb-read-ahead-threshold is deprecated and will be removed in a future release. Please use the full name instead.
2017-12-21 15:51:18 7fdea08037c0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-12-21 15:51:18 95069 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-12-21 15:51:18 95069 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-21 15:51:18 95069 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-12-21 15:51:18 95069 [Note] InnoDB: Memory barrier is not used
2017-12-21 15:51:18 95069 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-12-21 15:51:18 95069 [Note] InnoDB: Using CPU crc32 instructions
2017-12-21 15:51:18 95069 [Note] InnoDB: Initializing buffer pool, size = 48.0G
2017-12-21 15:51:19 95069 [Note] InnoDB: Completed initialization of buffer pool
2017-12-21 15:51:20 95069 [Note] InnoDB: Highest supported file format is Barracuda.
2017-12-21 15:51:20 95069 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2935394717
2017-12-21 15:51:20 95069 [Note] InnoDB: Database was not shutdown normally!
2017-12-21 15:51:20 95069 [Note] InnoDB: Starting crash recovery.
2017-12-21 15:51:20 95069 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-12-21 15:51:20 95069 [Note] InnoDB: Restoring possible half-written data pages
2017-12-21 15:51:20 95069 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2935394936
2017-12-21 15:51:20 95069 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 ^C

[witty-sun]

上边是在从库start slave 后 日志报的错