CURRENT_TEST: ml001
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
051206 20:41:41  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
051206 20:41:41  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...
051206 20:41:41  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
051206 20:41:41  InnoDB: Started; log sequence number 0 0
051206 20:41:41 [Note] /home/matthias/Arbeit/mysql-5.0/src-Z/sql/mysqld: ready for connections.
Version: '5.0.17-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
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=0x8e9e1a8
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=0x42e21c8c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81e04c3 handle_segfault + 437
0xffffe420 _end + -142644272
0x816ec64 _ZN9Item_func10fix_fieldsEP3THDPP4Item + 724
0x816ec64 _ZN9Item_func10fix_fieldsEP3THDPP4Item + 724
0x822cbbc _Z11setup_condsP3THDP13st_table_listS2_PP4Item + 362
0x8259029 _Z19setup_without_groupP3THDPP4ItemP13st_table_listS5_R4ListIS1_ES8_S3_P8st_orderSA_Pb + 117
0x8235f9e _ZN4JOIN7prepareEPPP4ItemP13st_table_listjS1_jP8st_orderS7_S1_S7_P13st_select_lexP18st_select_lex_unit + 772
0x833be69 _ZN18st_select_lex_unit7prepareEP3THDP13select_resultm + 1179
0x833da40 _Z21mysql_derived_prepareP3THDP6st_lexP13st_table_list + 304
0x833d8a1 _Z20mysql_handle_derivedP6st_lexPFbP3THDS0_P13st_table_listE + 125
0x8227d5a _Z30open_normal_and_derived_tablesP3THDP13st_table_listj + 174
0x830f601 _Z14get_all_tablesP3THDP13st_table_listP4Item + 2269
0x83166aa _Z24get_schema_tables_resultP4JOIN + 414
0x82393ce _ZN4JOIN4execEv + 1846
0x81afa16 _ZN30subselect_single_select_engine4execEv + 630
0x81abb3a _ZN14Item_subselect4execEv + 30
0x81ac706 _ZN24Item_singlerow_subselect7val_intEv + 72
0x835869c _Z17sp_eval_func_itemP3THDPP4Item16enum_field_typesS2_b + 352
0x835eb25 _ZN16sp_instr_freturn9exec_coreEP3THDPj + 53
0x835db52 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 432
0x835eaee _ZN16sp_instr_freturn7executeEP3THDPj + 138
0x835ad61 _ZN7sp_head7executeEP3THD + 1271
0x835b5cc _ZN7sp_head16execute_functionEP3THDPP4ItemjS4_ + 838
0x817c665 _ZN12Item_func_sp7executeEPP4Item + 235
0x817c479 _ZN12Item_func_sp7executeEPP5Field + 25
0x81804e7 _ZN12Item_func_sp7val_intEv + 27
0x81573a4 _ZN4Item4sendEP8ProtocolP6String + 568
0x81ceac9 _ZN11select_send9send_dataER4ListI4ItemE + 317
0x8238fd2 _ZN4JOIN4execEv + 826
0x823ae79 _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_mP13select_resultP18st_select_lex_unitP13st_sel + 745
0x8235bd7 _Z13handle_selectP3THDP6st_lexP13select_resultm + 347
0x81f9484 _Z21mysql_execute_commandP3THD + 1568
0x82023f2 _Z11mysql_parseP3THDPcj + 460
0x81f7485 _Z16dispatch_command19enum_server_commandP3THDPcj + 2041
0x81f6c81 _Z10do_commandP3THD + 577
0x81f5d06 handle_one_connection + 836
0x4017caa7 _end + 932663895
0x402adc2e _end + 933913566
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 0x8ebd998 = SELECT func1()
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:  8490 Speicherzugriffsfehler  (core dumped) /home/matthias/Arbeit/mysql-5.0/src-Z/sql/mysqld --no-defaults --log-bin=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/log/master-bin --server-id=1 --basedir=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test --port=9306 --local-infile --exit-info=256 --core --datadir=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/master-data --pid-file=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/run/master.pid --socket=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/tmp/master.sock --log=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/log/master.log --character-sets-dir=/home/matthias/Arbeit/mysql-5.0/src-Z/sql/share/charsets --default-character-set=latin1 --tmpdir=/home/matthias/Arbeit/mysql-5.0/src-Z/mysql-test/var/tmp --language=/home/matthias/Arbeit/mysql-5.0/src-Z/sql/share/english/ --innodb_data_file_path=ibdata1:128M:autoextend --open-files-limit=1024 --log-bin-trust-function-creators --rpl-recovery-rank=1 --init-rpl-role=master --key_buffer_size=1M --sort_buffer=256K --max_heap_table_size=1M --skip-ndbcluster