nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: alias
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060606 23:14:10  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060606 23:14:20  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
060606 23:14:21  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
060606 23:14:22  InnoDB: Started; log sequence number 0 0
060606 23:14:22 [Note] /home/matthias/Arbeit/mysql-5.0/src-1/sql/mysqld: ready for connections.
Version: '5.0.23-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.0/src-1/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
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=1048576
read_buffer_size=131072
max_used_connections=11
max_connections=100
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 39420 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8f9ac48
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=0x42db8a9c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x820f74f handle_segfault + 437
0xffffe420 _end + -143284688
0x8272844 _Z18add_not_null_condsP4JOIN + 616
0x827ff16 _Z19make_cond_for_tableP4Itemyy + 976
0x8272f99 _Z16make_join_selectP4JOINP10SQL_SELECTP4Item + 1283
0x82679af _ZN4JOIN8optimizeEv + 3733
0x81dcc9b _ZN30subselect_single_select_engine4execEv + 207
0x81d8e0a _ZN14Item_subselect4execEv + 30
0x81d99e6 _ZN24Item_singlerow_subselect7val_intEv + 72
0x81816e1 _ZN4Item13save_in_fieldEP5Fieldb + 675
0x825ce94 _Z11fill_recordP3THDR4ListI4ItemES4_b + 232
0x825cf62 _Z36fill_record_n_invoke_before_triggersP3THDR4ListI4ItemES4_bP19Table_triggers_list14trg_event_type + 52
0x8298fe4 _Z12mysql_updateP3THDP13st_table_listR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesb + 4352
0x822b421 _Z21mysql_execute_commandP3THD + 9381
0x823277c _Z11mysql_parseP3THDPcj + 460
0x8227577 _Z16dispatch_command19enum_server_commandP3THDPcj + 2221
0x8226cbf _Z10do_commandP3THD + 577
0x8225d38 handle_one_connection + 836
0x40059aa7 _end + 930831543
0x4018ac2e _end + 932081214
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/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 0x8ff74a8 = UPDATE systest1.tb1_eng1 target
SET i1 = (SELECT new_i1 FROM systest1.t1_tmp source WHERE source.i1 = target.i1),
f1 = @connection_id,
f2 = @operation,
f3 = ROUND(i1/@max_val,3),
f4 = @my_now
WHERE i1 = @next_val + 6 - @no_of_tries DIV 2
thd->thread_id=53
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.
Writing a core file