// after this ... server restarted itself

Mar 24 23:10:16 Debian-70-wheezy-64-minimal mysqld: Version: '5.5.34-MariaDB-1~wheezy-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 140324 23:11:38 [ERROR] mysqld got signal 11 ;
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: We will try our best to scrape up some info that will hopefully help
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: diagnose the problem, but since we have already crashed, 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: something is definitely wrong and this may fail.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Server version: 5.5.34-MariaDB-1~wheezy-log
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: key_buffer_size=3145728000
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: read_buffer_size=131072
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: max_used_connections=1
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: max_threads=153
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: thread_count=1
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: It is possible that mysqld could use up to 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3407642 K  bytes of memory
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Thread pointer: 0x0x7f5493bad000
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Attempting backtrace. You can use the following information to find out
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: where mysqld died. If you see no messages after this, something went
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: terribly wrong...
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: stack_bottom = 0x7f53f7ba8e10 thread_stack 0x30000
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f70822b]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f343ed2]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566ea3d030]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f1d0c5b]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f1f65d3]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f22dfe6]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f22e352]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f22e629]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f246e9d]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f2589b8]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f253b55]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f25a8d3]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f212024]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f212397]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f21397f]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f2c629b]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566f2c6321]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566ea34b50]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: ??:0(??)[0x7f566d358a7d]
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Trying to get some variables.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Some pointers may be invalid and cause the dump to abort.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Query (0x7f53f7443018): is an invalid pointer
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Connection ID (thread ID): 1
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Status: NOT_KILLED
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: 
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld: information that should help you find out what is causing the crash.
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld_safe: Number of processes running now: 0
Mar 24 23:11:38 Debian-70-wheezy-64-minimal mysqld_safe: mysqld restarted