Combined master.err and stacktrace #################################################### This file was generated by: nm -n ../sql/mysqld > /tmp/mysqld_sym.18 resolve_stack_dump -s '/tmp/mysqld_sym.18' -n './var//log/master.err' >> ######################################################################################## CURRENT_TEST: ml_trigger 071127 21:26:26 [Warning] One can only use the --user switch if running as root InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 071127 21:26:26 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 071127 21:26:26 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... 071127 21:26:26 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 071127 21:26:26 InnoDB: Started; log sequence number 0 0 071127 21:26:26 [Note] /work/trees/mysql-5.0-main-work/sql/mysqld: ready for connections. Version: '5.0.54-debug-log' socket: '/work/trees/mysql-5.0-main-work/mysql-test/var/tmp/master.sock' port: 10180 Source distribution mysqld: sql_delete.cc:843: virtual bool multi_delete::send_eof(): Assertion `!normal_tables || !deleted || thd->transaction.stmt.modified_non_trans_table' failed. 071127 21:26:26 - 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=0x17f10e8 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=0x43885e40, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x63a1fe handle_segfault + 662 0x2b8a09c73b45 _end + 147743325 0x180d150 _end + 8910952 New value of fp=0x43888950 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 0x1830658 = delete t2, t1 from t2 straight_join t1 where t1.i = t2.i thd->thread_id=1 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. Writing a core file