nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: ml008
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060410 18:23:33  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060410 18:23:33  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...
060410 18:23:33  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
060410 18:23:34  InnoDB: Started; log sequence number 0 0
060410 18:23:34 [Note] /home/matthias/Arbeit/mysql-5.1/src-A/sql/mysqld: ready for connections.
Version: '5.1.9-beta-debug-log'  socket: '/dev/shm/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=1
max_connections=100
threads_connected=1
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=0x92f45d0
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=0x421971bc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8237015 handle_segfault + 437
0xffffe420 _end + -144272240
(nil)
0x828c659 _Z14open_table_defP3THDP14st_table_sharej + 925
0x827ecee _Z15get_table_shareP3THDP13st_table_listPcjjPi + 336
0x827f0f6 _Z27get_table_share_with_createP3THDP13st_table_listPcjjPi + 108
0x8283ba0 _Z17open_unireg_entryP3THDP8st_tableP13st_table_listPKcPcjP11st_mem_root + 188
0x8282450 _Z10open_tableP3THDP13st_table_listP11st_mem_rootPbj + 2902
0x82848de _Z11open_ltableP3THDP13st_table_list13thr_lock_type + 150
0x8343595 _Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP13st_table_listR4ListI12create_fieldERS6_I3KeyEjP8st_order15enum_dup + 639
0x82534f9 _Z21mysql_execute_commandP3THD + 7029
0x825b9ed _Z11mysql_parseP3THDPcj + 497
0x824ff87 _Z16dispatch_command19enum_server_commandP3THDPcj + 2063
0x824f76c _Z10do_commandP3THD + 570
0x824e7e1 handle_one_connection + 827
0x40050aa7 _end + 929807127
0x40181c2e _end + 931056798
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 0x9314820 = ALTER TABLE t1 DROP PARTITION p2
thd->thread_id=1
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