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!
060327 22:07:38  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060327 22:07:52  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...
060327 22:07:53  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
060327 22:07:54  InnoDB: Started; log sequence number 0 0
060327 22:07:54 [Note] /home/matthias/Arbeit/mysql-5.1/src-D/sql/mysqld: ready for connections.
Version: '5.1.9-beta-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.1/src-D/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
/home/matthias/Arbeit/mysql-5.1/src-D/sql/mysqld: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "log_slow_statement"
/home/matthias/Arbeit/mysql-5.1/src-D/sql/mysqld: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "log_slow_statement"

!!!!!!!!!!!!!!!!!!!!
about 4000 other lines
/home/matthias/Arbeit/mysql-5.1/src-D/sql/mysqld: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "log_slow_statement"
deleted
!!!!!!!!!!!!!!!!!!!!

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=11
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=0x95e9ac8
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=0x423791fc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x82358c1 handle_segfault + 437
0xffffe420 _end + -144226064
(nil)
0x831f060 _Z13rr_sequentialP14st_read_record + 44
0x83452d1 _Z24copy_data_between_tablesP8st_tableS0_R4ListI12create_fieldE15enum_duplicatesbjP8st_orderPyS8_ + 1625
0x8343cca _Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP13st_table_listR4ListI12create_fieldERS6_I3KeyEjP8st_order15enum_dup + 10338
0x8251d73 _Z21mysql_execute_commandP3THD + 7029
0x825a2bd _Z11mysql_parseP3THDPcj + 569
0x824e823 _Z16dispatch_command19enum_server_commandP3THDPcj + 2063
0x824e008 _Z10do_commandP3THD + 570
0x824d07d handle_one_connection + 827
0x40050aa7 _end + 929853303
0x40181c2e _end + 931102974
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 0x92e5b20 = ALTER TABLE tb1_eng1 PARTITION BY HASH(i1) PARTITIONS 2
thd->thread_id=31
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