Changing file-key-management to example-key-management causes crash and no real error

BROKEN: block: 3400 checkpoint: 5 4227c7bc c45826ac

BROKEN: block: 3400 checkpoint: 5 4227c7bc c45826ac

InnoDB: Log block no 3400 at lsn 1740288 has

InnoDB: ok header, but checksum field contains 3294111404, should be 1109903292

InnoDB: Set innodb_force_recovery to ignore this error.

2015-07-02 10:06:35 7fa8eae9b780  InnoDB: Assertion failure in thread 140363472418688 in file log0recv.cc line 2833

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

150702 10:06:35 [ERROR] mysqld got signal 6 ;

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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.1.6-MariaDB-debug

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467186 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0

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 = 0x0 thread_stack 0x48000

addr2line: 'sql/mysqld': No such file

sql/mysqld(my_print_stacktrace+0x38)[0x7fa8ebc025be]

sql/mysqld(handle_fatal_signal+0x34c)[0x7fa8eb5ea603]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa8e93bf340]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa8e8a16cc9]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa8e8a1a0d8]

sql/mysqld(+0xa92add)[0x7fa8eb96aadd]

sql/mysqld(+0xa93045)[0x7fa8eb96b045]

sql/mysqld(+0xa93839)[0x7fa8eb96b839]

sql/mysqld(+0xb74289)[0x7fa8eba4c289]

sql/mysqld(+0xa0c21f)[0x7fa8eb8e421f]

sql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0xf3)[0x7fa8eb5ec55a]

sql/mysqld(+0x4fec05)[0x7fa8eb3d6c05]

sql/mysqld(_Z11plugin_initPiPPci+0x8e5)[0x7fa8eb3d77c8]

sql/mysqld(+0x3e37ba)[0x7fa8eb2bb7ba]

sql/mysqld(_Z11mysqld_mainiPPc+0x5f3)[0x7fa8eb2bc750]

sql/mysqld(main+0x20)[0x7fa8eb2b21d5]

/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa8e8a01ec5]

sql/mysqld(+0x3da0c8)[0x7fa8eb2b20c8]

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.