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=8388600
read_buffer_size=131072
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8620630
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...
Cannot determine thread, fp=0xbe5ff028, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x809116e handle_segfault + 414
0x8304272 pthread_sighandler + 162
0x80d3333 optimize_keyuse__FP4JOINP16st_dynamic_array + 163
0x80c4558 make_join_statistics__FP4JOINP13st_table_listP4ItemP16st_dynamic_array + 4440
0x80c0a89 optimize__4JOIN + 457
0x80c329c mysql_select__FP3THDPPP4ItemP13st_table_listUiRt4List1Z4ItemP4ItemUiP8st_orderT7T5T7UlP13select_resultP18st_select_lex_unitP13s + 604
0x8131e28 mysql_derived__FP3THDP6st_lexP18st_select_lex_unitP13st_table_list + 472
0x8131c0c mysql_handle_derived__FP6st_lex + 76
0x80bceda open_and_lock_tables__FP3THDP13st_table_list + 90
0x80d8ba2 mysql_test_select_fields__FP18Prepared_statementP13st_table_listUiRt4List1Z4ItemP4ItemUiP8st_orderT6T4T6UlP18st_select_lex_unit + 242
0x80d8f33 send_prepare_results__FP18Prepared_statement + 291
0x80d9185 mysql_stmt_prepare__FP3THDPcUi + 277
0x809e707 dispatch_command__F19enum_server_commandP3THDPcUi + 1255
0x809e214 do_command__FP3THD + 196
0x809da70 handle_one_connection + 768
0x83021ee pthread_start_thread + 158
0x833333a thread_start + 4
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8635bc8 = select count(1) from (select f.id from test1 f where f.id=?) as x
thd->thread_id=3
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
040301 11:41:57  mysqld restarted
/usr/local/mysql/libexec/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13)
040301 11:41:57  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...
040301 11:41:57  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 5200033.
InnoDB: Doing recovery: scanned up to log sequence number 0 5200033
040301 11:42:02  InnoDB: Flushing modified pages from the buffer pool...
040301 11:42:02  InnoDB: Started; log sequence number 0 5200033
/usr/local/mysql/libexec/mysqld: ready for connections.
Version: '4.1.2-alpha-nightly-20040229'  socket: '/tmp/mysql.sock'  port: 3306