CURRENT_TEST: nist_test
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
050509 12:27:08  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
050509 12:27:09  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...
050509 12:27:09  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
050509 12:27:09  InnoDB: Started; log sequence number 0 0
050509 12:27:09  InnoDB: Starting recovery for XA transactions...
050509 12:27:09  InnoDB: 0 transactions in prepared state after recovery
050509 12:27:10 [Note] /home/matthias/Arbeit/mysql-5.0/src-WL1420/sql/mysqld: ready for connections.
Version: '5.0.6-beta-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
050509 12:27:10InnoDB: Assertion failure in thread 1122118576 in file row0sel.c line 2082
InnoDB: Failing assertion: dict_col_get_type(field->col)->mtype == dfield_get_type(dfield)->mtype
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
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=0x8e4eb20
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=0x42e2013c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81d85f6
0xffffe420
0x4
0x8289f52
0x82898ba
0x8284ff5
0x8282179
0x8292602
0x8251d75
0x81f1db9
0x81f71e6
0x81ee0e6
0x81eda04
0x81ecc6b
0x4017aaa7
0x402abc2e
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 0x8e688c0 = DELETE FROM t2 WHERE F1 = 5
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
/bin/sh: line 1: 17179 Speicherzugriffsfehler  (core dumped) /home/matthias/Arbeit/mysql-5.0/src-WL1420/sql/mysqld --no-defaults --log-bin=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/log/master-bin --server-id=1 --basedir=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test --port=9306 --local-infile --exit-info=256 --core --datadir=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/master-data --pid-file=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/run/master.pid --socket=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/tmp/master.sock --log=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/log/master.log --character-sets-dir=/home/matthias/Arbeit/mysql-5.0/src-WL1420/sql/share/charsets --default-character-set=latin1 --tmpdir=/home/matthias/Arbeit/mysql-5.0/src-WL1420/mysql-test/var/tmp --language=/home/matthias/Arbeit/mysql-5.0/src-WL1420/sql/share/english/ --innodb_data_file_path=ibdata1:128M:autoextend --open-files-limit=1024 --log-bin-trust-routine-creators --rpl-recovery-rank=1 --init-rpl-role=master --key_buffer_size=1M --sort_buffer=256K --max_heap_table_size=1M --skip-ndbcluster