nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: ml014
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060424 23:25:44  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060424 23:25:44  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...
060424 23:25:44  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
060424 23:25:44  InnoDB: Started; log sequence number 0 0
060424 23:25:44 [Note] /home/matthias/Arbeit/mysql-5.1/src-1/sql/mysqld: ready for connections.
Version: '5.1.10-beta-debug-log'  socket: '/dev/shm/var/tmp/master.sock'  port: 10170  Source distribution
060424 23:25:45  InnoDB: Warning: MySQL is trying to drop table `test/t1#P#p0`
InnoDB: though there are still open handles to it.
InnoDB: Adding the table to the background drop queue.
060424 23:25:45  InnoDB: Error; possible reasons:
InnoDB: 1) Table rename would cause two FOREIGN KEY constraints
InnoDB: to have the same internal name in case-insensitive comparison.
InnoDB: 2) table `test/t1#P#p0` exists in the InnoDB internal data
InnoDB: dictionary though MySQL is trying rename table `test/t1#P#p0#TMP#` to it.
InnoDB: Have you deleted the .frm file and not used DROP TABLE?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
InnoDB: If table `test/t1#P#p0` is a temporary table #sql..., then it can be that
InnoDB: there are still queries running on the table, and it will be
InnoDB: dropped automatically when the queries end.
InnoDB: You can drop the orphaned table inside InnoDB by
InnoDB: creating an InnoDB table with the same name in another
InnoDB: database and copying the .frm file to the current database.
InnoDB: Then MySQL thinks the table exists, and DROP TABLE will
InnoDB: succeed.
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=0x92b21b0
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=0x421960e4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8232d70 handle_segfault + 412
0xffffe420 _end + -144000464
0x42196450 _end + 964967008
0x83b1ce2 _ZN11ha_innobase4infoEj + 1372
0x8316dcd _ZN7handler11get_dup_keyEi + 133
0x8316307 _ZN7handler11print_errorEii + 199
0x83f8eb4 _ZN12ha_partition11print_errorEii + 258
0x819673a _Z23mysql_rename_partitionsP18st_lock_param_type + 208
0x8198a20 _Z26fast_alter_partition_tableP3THDP8st_tableP13st_alter_infoP24st_ha_create_informationP13st_table_listP4ListI12create_fieldEP + 2568
0x8331d1a _Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP13st_table_listR4ListI12create_fieldERS6_I3KeyEjP8st_order15enum_dup + 8906
0x824df43 _Z21mysql_execute_commandP3THD + 6301
0x8255338 _Z11mysql_parseP3THDPcj + 484
0x824af29 _Z16dispatch_command19enum_server_commandP3THDPcj + 1801
0x824a810 _Z10do_commandP3THD + 518
0x824998e handle_one_connection + 818
0x40050aa7 _end + 930078903
0x40181c2e _end + 931328574
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 0x92d2530 = ALTER TABLE t1 ADD PARTITION PARTITIONS 1
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