nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: alias
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060505 19:08:12  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060505 19:08:13  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...
060505 19:08:14  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
060505 19:08:16  InnoDB: Started; log sequence number 0 0
060505 19:08:16 [Note] /home/matthias/Arbeit/mysql-5.1/src-E/sql/mysqld: ready for connections.
Version: '5.1.10-beta-debug-log'  socket: '/home/matthias/Arbeit/mysql-5.1/src-E/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
mysqld: handler.cc:780: int ha_rollback_trans(THD*, bool): Assertion `0' 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=10
max_connections=100
threads_connected=10
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=0x925fa50
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=0x4224ed54, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x823480c handle_segfault + 412
0xffffe420 _end + -144038640
(nil)
0x400e8903 _end + 930662899
0x83162a1 _Z17ha_rollback_transP3THDb + 209
0x832d07c _Z27convert_error_code_to_mysqliP3THD + 124
0x833052f _ZN11ha_innobase9write_rowEPc + 1395
0x831b3e9 _ZN7handler12ha_write_rowEPc + 29
0x82b291c _Z12write_recordP3THDP8st_tableP12st_copy_info + 1738
0x82b1455 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2209
0x82506b3 _Z21mysql_execute_commandP3THD + 8971
0x83db723 _ZN13sp_instr_stmt9exec_coreEP3THDPj + 17
0x83db363 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 383
0x83db5a5 _ZN13sp_instr_stmt7executeEP3THDPj + 341
0x83d842d _ZN7sp_head7executeEP3THD + 1137
0x83d8d88 _ZN7sp_head16execute_functionEP3THDPP4ItemjP5Field + 1136
0x83e967c _ZN19Table_triggers_list16process_triggersEP3THD14trg_event_type20trg_action_time_typeb + 438
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 0x95aa6a8 = insert into tb1_logs (dt1, entry_dsc, f4)
values (now(), concat('Insert row ', new.f1,' ',
new.f2, ' ', new.f3, ' (tb1_eng2)'), new.f1)
thd->thread_id=14
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