miguel@luz:~$ dbs/mysql-next/libexec/mysqld
090831 17:01:33 [Note] Plugin 'FEDERATED' is disabled.
090831 17:01:33 [Note] Plugin 'ndbcluster' is disabled.
090831 17:01:34  InnoDB: Started; log sequence number 0 46409
090831 17:01:34 [Note] Event Scheduler: Loaded 0 events
090831 17:01:34 [Note] dbs/mysql-next/libexec/mysqld: ready for connections.
Version: '5.4.4-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
090831 17:02:34  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`.090831 17:02:34 [ERROR] Invalid (old?) table or database name 'TestTable#P#p3#SP#p3sp1'
`#mysql50#TestTable#P#p3#SP#p3sp1` exists in the InnoDB internal data
InnoDB: dictionary though MySQL is trying to rename table `test`.090831 17:02:34 [ERROR] Invalid (old?) table or database name 'TestTable#P#p3#SP#p3sp1#TMP#'
`#mysql50#TestTable#P#p3#SP#p3sp1#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/refman/5.1/en/innodb-troubleshooting.html
InnoDB: If table `test`.090831 17:02:34 [ERROR] Invalid (old?) table or database name 'TestTable#P#p3#SP#p3sp1'
`#mysql50#TestTable#P#p3#SP#p3sp1` 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.
InnoDB: Error: trying to use a corrupt
InnoDB: table handle. Magic n 0, table name090831 17:02:34 - 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=8384512
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338485 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3ef78a8
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...
stack_bottom = 0x7f60385d70f0 thread_stack 0x40000
dbs/mysql-next/libexec/mysqld(my_print_stacktrace+0x32) [0xb8273c]
dbs/mysql-next/libexec/mysqld(handle_segfault+0x2a6) [0x6f2852]
/lib/libpthread.so.0 [0x7f603cc87080]
dbs/mysql-next/libexec/mysqld(row_update_prebuilt_trx+0x92) [0xa07cc0]
dbs/mysql-next/libexec/mysqld(ha_innobase::update_thd(THD*)+0x46) [0x9a99b8]
dbs/mysql-next/libexec/mysqld(ha_innobase::info(unsigned int)+0x8a) [0x9a41c6]
dbs/mysql-next/libexec/mysqld(ha_partition::info(unsigned int)+0x67a) [0x861dfc]
dbs/mysql-next/libexec/mysqld(handler::get_dup_key(int)+0x92) [0x8541e2]
dbs/mysql-next/libexec/mysqld(handler::print_error(int, int)+0x104) [0x8595f0]
dbs/mysql-next/libexec/mysqld(ha_partition::print_error(int, int)+0xe4) [0x862d30]
dbs/mysql-next/libexec/mysqld [0x607716]
dbs/mysql-next/libexec/mysqld(fast_alter_partition_table(THD*, TABLE*, Alter_info*, st_ha_create_information*, TABLE_LIST*, char*, char const*, unsigned int)+0x8ec) [0x60a88a]
dbs/mysql-next/libexec/mysqld(mysql_alter_table(THD*, char*, char*, st_ha_create_information*, TABLE_LIST*, Alter_info*, unsigned int, st_order*, bool)+0x1542) [0x881c7e]
dbs/mysql-next/libexec/mysqld(mysql_execute_command(THD*)+0x269f) [0x7072f8]
dbs/mysql-next/libexec/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x276) [0x70dd19]
dbs/mysql-next/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xa99) [0x70e946]
dbs/mysql-next/libexec/mysqld(do_command(THD*)+0x22b) [0x70fe8e]
dbs/mysql-next/libexec/mysqld(handle_one_connection+0x13f) [0x6fcf7f]
/lib/libpthread.so.0 [0x7f603cc7f3ba]
/lib/libc.so.6(clone+0x6d) [0x7f603bbebfcd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x3f52970 = alter table TestTable reorganize partition p2,p3 into ( partition p3 values less than
(to_days('2009-03-01')))
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
miguel@luz:~$