CURRENT_TEST: ml017
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060130 16:15:46  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060130 16:15:46  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...
060130 16:15:46  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
060130 16:15:47  InnoDB: Started; log sequence number 0 0
060130 16:15:47 [Note] /home/matthias/Arbeit/mysql-5.1/src-B/sql/mysqld: ready for connections.
Version: '5.1.6-alpha-debug-log'  socket: '/dev/shm/var/tmp/master.sock'  port: 9306  Source distribution
mysqld: ha_partition.cc:3724: int ha_partition::partition_scan_set_up(byte*, bool): Assertion `m_part_spec.start_part < m_tot_parts' failed.
mysqld got signal 6;
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=0x92581e8
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=0x422b0254, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x820d05b
0xffffe420
(nil)
0x4020b903
0x83dd738
0x83dcc4c
0x83dcbad
0x8281400
0x82802d8
0x827fe62
0x826dd54
0x826e2d3
0x8268e17
0x8227d9e
0x8231171
0x8225df7
0x8225602
0x8224664
0x40173aa7
0x402a4c2e
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 0x9278630 = SELECT * FROM t1 WHERE f_int1 = 4
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