CURRENT_TEST: funcs_1.zz1
070808  5:13:53 [Note] Plugin 'InnoDB' disabled by command line option
070808  5:14:02 [Note] Starting MySQL Cluster Binlog Thread
070808  5:14:02 [Note] Event Scheduler: Loaded 0 events
070808  5:14:02 [Note] /home/omer/source/bld51_806/sql/mysqld: ready for connections.
Version: '5.1.21-beta-log'  socket: '/home/omer/source/bld51_806/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
070808  5:14:02 [Note] NDB: Creating mysql.ndb_schema
070808  5:14:02 [Note] NDB Binlog: CREATE TABLE Event: REPL$mysql/ndb_schema
070808  5:14:02 [Note] NDB Binlog: logging ./mysql/ndb_schema
070808  5:14:02 [Note] NDB: Creating mysql.ndb_apply_status
070808  5:14:03 [Note] NDB Binlog: starting log at epoch 18
070808  5:14:03 [Note] NDB Binlog: Node: 2, subscribe from node 4, Subscriber bitmask 010
070808  5:14:03 [Note] NDB Binlog: Node: 1, subscribe from node 4, Subscriber bitmask 010
070808  5:14:03 [Note] NDB Binlog: CREATE TABLE Event: REPL$mysql/ndb_apply_status
070808  5:14:03 [Note] NDB Binlog: logging ./mysql/ndb_apply_status
070808  5:14:04 [Note] NDB Binlog: Node: 1, subscribe from node 5, Subscriber bitmask 030
070808  5:14:04 [Note] NDB Binlog: Node: 2, subscribe from node 5, Subscriber bitmask 030
070808  5:14:04 - 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=2
max_threads=151
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 59857 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8921db0
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=0x406c802c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8220c28
0x8172d46
0x827a1db
0x8330efb
0x832a94f
0x82a0192
0x82a2c4f
0x82a315f
0x822c331
0x822fe9a
0x8238c11
0x823915d
0x823a55f
0x8229c0b
0x40032297
0x4018437e
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.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 0x892b888 = select * from columns
thd->thread_id=3
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