nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: ndb_ml1105
060303 12:20:54 [Note] Starting MySQL Cluster Binlog Thread
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060303 12:20:54  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060303 12:20:55  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...
060303 12:20:55  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
060303 12:20:55  InnoDB: Started; log sequence number 0 0
060303 12:20:55 [Note] /home/matthias/Arbeit/mysql-5.1/src-D/sql/mysqld: ready for connections.
Version: '5.1.8-beta-debug-log'  socket: '/dev/shm/var/tmp/master.sock'  port: 9306  Source distribution
060303 12:20:55 [Note] NDB: Creating cluster.apply_status
060303 12:20:55 [Note] NDB Binlog: CREATE TABLE Event: REPL$cluster/apply_status
060303 12:20:55 [Note] NDB Binlog: logging ./cluster/apply_status
060303 12:20:55 [Note] NDB: Creating cluster.schema
060303 12:20:56 [Note] NDB Binlog: CREATE TABLE Event: REPL$cluster/schema
Waited WAITFOR_RESPONSE_TIMEOUT, continuing wait
060303 12:20:56 [Note] NDB Binlog: logging ./cluster/schema
060303 12:20:56 [Note] NDB Binlog: Node: 1, subscribe from node 4, Subscriber bitmask 010
060303 12:20:56 [Note] NDB Binlog: Node: 2, subscribe from node 4, Subscriber bitmask 010
060303 12:20:56 [Note] NDB Binlog: Node: 1, subscribe from node 5, Subscriber bitmask 030
060303 12:20:56 [Note] NDB Binlog: Node: 2, subscribe from node 5, Subscriber bitmask 030
060303 12:20:57 [Note] NDB Binlog: CREATE TABLE Event: REPL$test/t1
060303 12:20:57 [Note] NDB Binlog: logging ./test/t1
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=0x932d948
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=0x424250ac, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x82105ad handle_segfault + 437
0xffffe420 _end + -143698576
0x869d381 _db_doprnt_ + 65
0x85ca09e _ZN14NdbTransaction14executeNoBlobsENS_8ExecTypeENS_11AbortOptionEi + 188
0x85c9b81 _ZN14NdbTransaction7executeENS_8ExecTypeENS_11AbortOptionEi + 249
0x83db7bb _Z14execute_commitP3THDP14NdbTransaction + 47
0x83c6ad2 _Z17ndbcluster_commitP3THDb + 264
0x82ff320 _Z19ha_commit_one_phaseP3THDb + 208
0x82ff18e _Z15ha_commit_transP3THDb + 742
0x82ff6bd _Z25ha_autocommit_or_rollbackP3THDi + 99
0x82a6301 _Z12mysql_deleteP3THDP13st_table_listP4ItemP11st_sql_listyyb + 4645
0x822de62 _Z21mysql_execute_commandP3THD + 11244
0x8235091 _Z11mysql_parseP3THDPcj + 569
0x822989b _Z16dispatch_command19enum_server_commandP3THDPcj + 2063
0x8229080 _Z10do_commandP3THD + 570
0x82280f5 handle_one_connection + 827
0x40173aa7 _end + 931572727
0x402a4c2e _end + 932822398
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 0x933ada8 = DELETE FROM t1 WHERE f_int1 IS NULL OR f_int1 = 1
thd->thread_id=2
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