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!
060607 22:21:18  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060607 22:21:19  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...
060607 22:21:20  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
060607 22:21:21  InnoDB: Started; log sequence number 0 0
060607 22:21:21 [Note] /home/matthias/Arbeit/mysql-5.1/src-E/sql/mysqld: ready for connections.
Version: '5.1.12-beta-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.1/src-E/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
060607 22:21:21 [Note] SCHEDULER: Manager thread booting
060607 22:21:21 [Note] SCHEDULER: Loaded 0 events
060607 22:21:21 [Note] SCHEDULER: Suspending operations
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=9
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=0x9318c10
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=0x4233927c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x823eec2 handle_segfault + 412
0xffffe420 _end + -144164336
0x24 (?)
0x852252a lock_deadlock_recursive + 759
0x8522646 lock_deadlock_recursive + 1043
0x85221b1 lock_deadlock_occurs + 82
0x85209b0 lock_rec_enqueue_waiting + 237
0x8520d6c lock_rec_lock_slow + 100
0x8520e2c lock_rec_lock + 68
0x852531e lock_clust_rec_read_check_and_lock + 116
0x854e5fa sel_set_rec_lock + 97
0x8551fd6 row_search_for_mysql + 3705
0x833e500 _ZN11ha_innobase13general_fetchEPcjj + 106
0x833e86d _ZN11ha_innobase8rnd_nextEPc + 143
0x831d81a _Z13rr_sequentialP14st_read_record + 40
0x82ce76c _Z12mysql_deleteP3THDP13st_table_listP4ItemP11st_sql_listyyb + 3096
0x825b9cf _Z21mysql_execute_commandP3THD + 9985
0x8261f86 _Z11mysql_parseP3THDPcj + 484
0x8257b41 _Z16dispatch_command19enum_server_commandP3THDPcj + 1921
0x82573b0 _Z10do_commandP3THD + 518
0x825652e handle_one_connection + 818
0x40050aa7 _end + 929915031
0x40181c2e _end + 931164702
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 0x9396228 = DELETE FROM systest1.tb1_eng1
WHERE i1 IN (SELECT i1 FROM systest1.t1_tmp WHERE pk = 1)
thd->thread_id=146
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