121227 11:39:45 InnoDB: The InnoDB memory heap is disabled
121227 11:39:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121227 11:39:45 InnoDB: Compressed tables use zlib 1.2.3.4
121227 11:39:45 InnoDB: Using Linux native AIO
121227 11:39:45 InnoDB: CPU supports crc32 instructions
121227 11:39:45 InnoDB: Initializing buffer pool, size = 256.0M
121227 11:39:45 InnoDB: Completed initialization of buffer pool
121227 11:39:45 InnoDB: highest supported file format is Barracuda.
121227 11:39:45 InnoDB: 128 rollback segment(s) are active.
121227 11:39:45 InnoDB: 1.2.0 started; log sequence number 3684383271
121227 11:39:45 [Note] Plugin 'FEEDBACK' is disabled.
121227 11:39:45 [Note] Event Scheduler: Loaded 0 events
121227 11:39:45 [Note] Reading of all Master_info entries succeded
121227 11:39:45 [Note] Added new Master_info '' to hash table
121227 11:39:45 [Note] mysqld: ready for connections.
Version: '10.0.0-MariaDB-mariadb1~precise'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
121227 11:42:36 [ERROR] 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.

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.0.0-MariaDB-mariadb1~precise
key_buffer_size=16777216
read_buffer_size=16777216
max_used_connections=1
max_threads=102
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2106934 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f16b9b4f5a0
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 = 0x7f16b59b9e50 thread_stack 0x48000
addr2line: 'mysqld': No such file
mysqld(my_print_stacktrace+0x2b)[0x7f16b63f102b]
mysqld(handle_fatal_signal+0x471)[0x7f16b5fd2321]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f16b50afcb0]
mysqld(_ZN3THD19cleanup_after_queryEv+0xd5)[0x7f16b5e64ba5]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1e71)[0x7f16b5e98f91]
mysqld(_Z24do_handle_one_connectionP3THD+0x133)[0x7f16b5f56c13]
mysqld(handle_one_connection+0x47)[0x7f16b5f56d97]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f16b50a7e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f16b3d77cbd]

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

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

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.