-----
090930 14:24:31 - 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=67108864
read_buffer_size=2097152
max_used_connections=56
max_threads=200
threads_connected=15
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681967 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab481d5800
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 = 0x46349f20 thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=1221033
thd->killed=NOT_KILLED

-----
091013 17:06:59 - 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=67108864
read_buffer_size=2097152
max_used_connections=35
max_threads=200
threads_connected=9
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab4430c660
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 = 0x45d36f20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8496fe]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5be9e2]
/lib64/libpthread.so.0[0x327e60de80]
/usr/sbin/mysqld(_ZN5mySTL7find_ifINS_4listIPN5yaSSL11SSL_SESSIONEE8iteratorENS2_20yassl_int_cpp_local210sess_matchEEET_S9_S9_T0_+0x32)[0x8848f2]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions6lookupEPKhPNS_11SSL_SESSIONE+0x30)[0x8840d0]
/usr/sbin/mysqld[0x832006]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5548]
/lib64/libpthread.so.0[0x327e606307]
/lib64/libc.so.6(clone+0x6d)[0x327ded1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=425027
thd->killed=NOT_KILLED

-----
091018  5:06:26 - 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=67108864
read_buffer_size=2097152
max_used_connections=31
max_threads=200
threads_connected=13
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab48f595b0
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 = 0x45cb1f20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8496fe]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5be9e2]
/lib64/libpthread.so.0[0x327e60de80]
/usr/sbin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x87fc50]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions5FlushEv+0x2d)[0x88426d]
/usr/sbin/mysqld(_ZN5yaSSL12sendFinishedERNS_3SSLENS_13ConnectionEndENS_12BufferOutputE+0x567)[0x88db37]
/usr/sbin/mysqld(yaSSL_accept+0x106)[0x873626]
/usr/sbin/mysqld[0x832022]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5548]
/lib64/libpthread.so.0[0x327e606307]
/lib64/libc.so.6(clone+0x6d)[0x327ded1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=145620
thd->killed=NOT_KILLED


-----
091019 15:19:44 - 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=67108864
read_buffer_size=2097152
max_used_connections=20
max_threads=200
threads_connected=15
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab4804d450
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 = 0x45423f20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8496fe]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5be9e2]
/lib64/libpthread.so.0[0x327e60de80]
/usr/sbin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x87fc50]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions5FlushEv+0x2d)[0x88426d]
/usr/sbin/mysqld(_ZN5yaSSL12sendFinishedERNS_3SSLENS_13ConnectionEndENS_12BufferOutputE+0x567)[0x88db37]
/usr/sbin/mysqld(yaSSL_accept+0x106)[0x873626]
/usr/sbin/mysqld[0x832022]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5548]
/lib64/libpthread.so.0[0x327e606307]
/lib64/libc.so.6(clone+0x6d)[0x327ded1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=43320
thd->killed=NOT_KILLED

-----
091022 12:31:23 - 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=67108864
read_buffer_size=2097152
max_used_connections=30
max_threads=200
threads_connected=18
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 681971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aab48312170
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 = 0x467e3f20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8496fe]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5be9e2]
/lib64/libpthread.so.0[0x327e60de80]
/usr/sbin/mysqld(_ZNK5yaSSL11SSL_SESSION9GetBornOnEv+0x0)[0x87fc50]
/usr/sbin/mysqld(_ZN5yaSSL8Sessions5FlushEv+0x2d)[0x88426d]
/usr/sbin/mysqld(_ZN5yaSSL12sendFinishedERNS_3SSLENS_13ConnectionEndENS_12BufferOutputE+0x567)[0x88db37]
/usr/sbin/mysqld(yaSSL_accept+0x106)[0x873626]
/usr/sbin/mysqld[0x832022]
/usr/sbin/mysqld(handle_one_connection+0x308)[0x5c5548]
/lib64/libpthread.so.0[0x327e606307]
/lib64/libc.so.6(clone+0x6d)[0x327ded1ded]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=101409
thd->killed=NOT_KILLED