CURRENT_TEST: reorg_part2_8
Error when connection to server using SSL:Unable to get certificate from '/data0/mysql/mysql-5.1-clone/mysql-test/std_data/server-cert.pem'
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060717 23:09:16  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060717 23:09:17  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...
060717 23:09:17  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
060717 23:09:18  InnoDB: Started; log sequence number 0 0
060717 23:09:18 [Note] /data0/mysql/mysql-5.1-clone/sql/mysqld: ready for connections.
Version: '5.1.12-beta-debug-log'  socket: '/data0/mysql/mysql-5.1-clone/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
060717 23:09:18 [Note] SCHEDULER: Manager thread booting
060717 23:09:18 [Note] SCHEDULER: Loaded 0 events
060717 23:09:18 [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=2
max_connections=100
threads_connected=2
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=0x9316b78
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=0xb339dd08, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8254069
0xffffe420
0x8248f92
0x8248f92
0x82492cf
0x819f4bf
0x81a067e
0x83c21ef
0x8270782
0x82781a8
0x8278cdc
Stack trace seems successful - bottom reached
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 0x93645b8 = ALTER TABLE tb5_eng1 REORGANIZE PARTITION part8,part9 INTO
(PARTITION part1 values in (1,2,3,4,5,6,7,8) DATA DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpdata' INDEX DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpindex' 
(SUBPARTITION subpart21, SUBPARTITION subpart22, SUBPARTITION subpart23, SUBPARTITION subpart24))
thd->thread_id=2
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