-bash-4.1$ mysqld --verbose
150312 22:33:00 [Note] Plugin 'FEDERATED' is disabled.
150312 22:33:00 InnoDB: The InnoDB memory heap is disabled
150312 22:33:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150312 22:33:00 InnoDB: Compressed tables use zlib 1.2.3
150312 22:33:00 InnoDB: Using Linux native AIO
150312 22:33:00 InnoDB: Initializing buffer pool, size = 128.0M
150312 22:33:00 InnoDB: Completed initialization of buffer pool
150312 22:33:00 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1129263120077
150312 22:33:00  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1129263127583
InnoDB: Error: trying to access page number 4294965119 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
150312 22:33:00  InnoDB: Assertion failure in thread 140492790335232 in file fil0fil.c line 4578
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:33:00 UTC - 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.
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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338550 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x35)[0x7aabf5]
mysqld(handle_fatal_signal+0x4a4)[0x686324]
/lib64/libpthread.so.0(+0xf710)[0x7fc7069a8710]
/lib64/libc.so.6(gsignal+0x35)[0x7fc705b6f625]
/lib64/libc.so.6(abort+0x175)[0x7fc705b70e05]
mysqld[0x8c909c]
mysqld[0x8a2738]
mysqld[0x8a3003]
mysqld[0x895b11]
mysqld[0x863823]
mysqld[0x863d69]
mysqld[0x866999]
mysqld[0x851691]
mysqld[0x81fd8e]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x688d38]
mysqld[0x593e7a]
mysqld(_Z11plugin_initPiPPci+0xa8c)[0x59870c]
mysqld[0x517a0a]
mysqld(_Z11mysqld_mainiPPc+0x44d)[0x51b37d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fc705b5bd5d]
mysqld[0x5106a9]
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.