安装handlersocke插件后，为什么数据库总是自己不停的重启

[lanbaibai]

我的系统Ubuntu 8.04.4，mysql 5.1.57,数据库是二进制版本的，编译handlersocket的时候，为了编译通过，在这台机器上面也安装了一个源码版的mysql5.1.57数据库
handlersocket编译安装通过后，安装好handlersocket的插件，在my.cnf配置好handlersocket的参数后，启动二进制版的mysql数据库。这个二进制版的mysql就开始不停重启。不知是啥原因？下面内容是err日志记录的内容。
20409 08:35:12 mysqld_safe Starting mysqld daemon with databases from /data/my3306
120409 8:35:12 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120409 8:35:12 [Note] Plugin 'FEDERATED' is disabled.
120409 8:35:12 InnoDB: Initializing buffer pool, size = 8.0M
120409 8:35:12 InnoDB: Completed initialization of buffer pool
120409 8:35:12 InnoDB: Started; log sequence number 0 1730481351
CONFIG: num_threads=16
CONFIG: nonblocking=1(default)
CONFIG: use_epoll=1
CONFIG: readsize=0
CONFIG: conn_per_thread=1024(default)
CONFIG: for_write=0(default)
CONFIG: plain_secret=(default)
CONFIG: timeout=300
CONFIG: listen_backlog=32768
CONFIG: host=(default)
CONFIG: port=9998
CONFIG: sndbuf=0
CONFIG: rcvbuf=0
[Warning] handlersocket: open_files_limit is too small.
CONFIG: stack_size=1048576(default)
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
CONFIG: wrlock_timeout=12
CONFIG: accept_balance=0
handlersocket: not listening for writes
handlersocket: initialized
120409 8:35:12 [Note] Event Scheduler: Loaded 0 events
120409 8:35:12 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.1.57-log' socket: '/data/my3306/mysql.3306.sock' port: 3306 MySQL Community Server (GPL)
120409 8:35:12 - 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=16
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133915 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x14e3860
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 = (nil) thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x8b68ee]
/usr/local/mysql/bin/mysqld(handle_segfault+0x351)[0x5e4f21]
/lib/libpthread.so.0[0x7fc75d9af7d0]
/lib/libpthread.so.0(pthread_mutex_lock+0x13)[0x7fc75d9a9423]
/usr/local/mysql/lib/plugin/handlersocket.so(_ZN4dena9dbcontext11init_threadEPKvRVi+0x1f6)[0x7fc75b3223f6]
/usr/local/mysql/lib/plugin/handlersocket.so(_ZN4dena15hstcpsvr_worker3runEv+0x28)[0x7fc75b32b618]
/usr/local/mysql/lib/plugin/handlersocket.so(_ZN4dena6threadINS_13worker_throbjEE11thread_mainEPv+0xd)[0x7fc75b330ded]
/lib/libpthread.so.0[0x7fc75d9a73f7]
/lib/libc.so.6(clone+0x6d)[0x7fc75ce4122d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query ((nil)): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
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.
120409 08:35:12 mysqld_safe Number of processes running now: 0
120409 08:35:12 mysqld_safe mysqld restarted