CURRENT_TEST: main.rpl_zzz
070905  3:26:28 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
070905  3:26:28  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070905  3:26:29  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...
070905  3:26:29  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
070905  3:26:30  InnoDB: Started; log sequence number 0 0
070905  3:26:30 [Note] Event Scheduler: Loaded 0 events
070905  3:26:30 [Note] /home/omer/source/src51_0902/sql/mysqld: ready for connections.
Version: '5.1.23-beta-log'  socket: '/home/omer/source/src51_0902/mysql-test/var/tmp/slave.sock'  port: 9308  Source distribution
070905  3:26:30 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:9306',replication started in log 'FIRST' at position 4
070905  3:26:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/home/omer/source/src51_0902/mysql-test/var/log/slave-relay-bin.000001' position: 4
070905  3:26:34  InnoDB: Assertion failure in thread 1106172848 in file row/row0sel.c line 4599
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
070905  3:26:34 - 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=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 = 59858 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8d64ab8
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=0x41eec724, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8222ab3
0xffffe410
0x400eedbb
0x846a415
0x83de537
0x83de77d
0x83de8d4
0x830ec51
0x82dc38d
0x834fa6f
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 (nil)  is invalid pointer
thd->thread_id=4
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