nm -n ../sql/mysqld > /tmp/mysqld.sym
####################################################
resolve_stack_dump -s /tmp/mysqld.sym -n var/log/master.err
########################################################################################
CURRENT_TEST: ndb_ml003
060403 11:51:08 [Note] Starting MySQL Cluster Binlog Thread
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060403 11:51:09  InnoDB: Setting file ./ibdata1 size to 128 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
060403 11:51: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...
060403 11:51: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
060403 11:51:09  InnoDB: Started; log sequence number 0 0
060403 11:51:09 [Note] /home/matthias/Arbeit/mysql-5.1/src-B/sql/mysqld: ready for connections.
Version: '5.1.9-beta-debug-log'  socket: '/dev/shm/var/tmp/master.sock'  port: 9306  Source distribution
060403 11:51:09 [Note] NDB: Creating cluster.schema
060403 11:51:10 [Note] NDB Binlog: CREATE TABLE Event: REPL$cluster/schema
Waited WAITFOR_RESPONSE_TIMEOUT, continuing wait
060403 11:51:10 [Note] NDB Binlog: logging ./cluster/schema
060403 11:51:10 [Note] NDB: Creating cluster.apply_status
060403 11:51:10 [Note] NDB Binlog: CREATE TABLE Event: REPL$cluster/apply_status
060403 11:51:10 [Note] NDB Binlog: logging ./cluster/apply_status
060403 11:51:10 [Note] NDB Binlog: Node: 1, subscribe from node 4, Subscriber bitmask 010
060403 11:51:10 [Note] NDB Binlog: Node: 2, subscribe from node 4, Subscriber bitmask 010
060403 11:51:11 [Note] NDB Binlog: Node: 1, subscribe from node 5, Subscriber bitmask 030
060403 11:51:11 [Note] NDB Binlog: Node: 2, subscribe from node 5, Subscriber bitmask 030
060403 11:51:12 [Note] NDB Binlog: CREATE TABLE Event: REPL$test/t1
060403 11:51:12 [Note] NDB Binlog: logging ./test/t1
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=0x93a57c8
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=0x422e24cc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x82356b1 handle_segfault + 437
0xffffe420 _end + -144234224
(nil)
0x85dddea _ZN6VectorIiEixEj + 34
0x85bf9b7 _ZN21NdbIndexScanOperation13getValue_implEPK13NdbColumnImplPc + 207
0x85e3a1e _ZN12NdbOperation8getValueEPKN13NdbDictionary6ColumnEPc + 60
0x83e4f0b _ZN13ha_ndbcluster20get_ndb_partition_idEP12NdbOperation + 127
0x83e9432 _ZN13ha_ndbcluster18ordered_index_scanEPK12st_key_rangeS2_bbPcP13part_id_range + 1268
0x83ec593 _ZN13ha_ndbcluster23read_range_first_to_bufEPK12st_key_rangeS2_bbPc + 919
0x83ebe30 _ZN13ha_ndbcluster10index_readEPcPKcj16ha_rkey_function + 276
0x831d49e _Z13opt_sum_queryP13st_table_listR4ListI4ItemEPS2_ + 1446
0x82943f5 _ZN4JOIN8optimizeEv + 1713
0x8298538 _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_mP13select_resultP18st_select_lex_unitP13st_sel + 624
0x8293052 _Z13handle_selectP3THDP6st_lexP13select_resultm + 350
0x8250708 _Z21mysql_execute_commandP3THD + 1768
0x825a097 _Z11mysql_parseP3THDPcj + 497
0x824e623 _Z16dispatch_command19enum_server_commandP3THDPcj + 2063
0x824de08 _Z10do_commandP3THD + 570
0x824ce7d handle_one_connection + 827
0x40050aa7 _end + 929845143
0x40181c2e _end + 931094814
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 0x93b4420 = SELECT MIN(f_int2) FROM t1
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