070726 17:54:37  mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
070726 17:54:38  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070726 17:54:38  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...
070726 17:54:38  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
070726 17:54:39  InnoDB: Started; log sequence number 0 0
070726 17:54:39 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 17:56:00 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:00 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:00 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:00 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:06 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:06 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:07 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:07 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:07 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:07 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:08 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:08 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:08 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:08 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:09 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:09 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:10 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:12 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:12 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:15 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:15 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:15 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:15 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:17 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:17 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:17 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:17 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:33 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:33 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:34 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:34 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:35 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:37 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:37 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:38 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:38 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:38 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:38 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:39 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:39 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:40 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:40 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:40 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:40 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:41 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:41 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:42 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:42 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:47 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:47 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:47 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:47 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:56:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:56:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:57:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:57:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:57:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:57:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:57:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:58:58 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:02 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:03 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:05 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:11 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:13 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:14 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:14 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:18 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:18 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:20 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:21 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:21 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:22 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:22 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:22 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:22 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:32 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:32 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:32 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:32 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:52 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:53 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:54 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:55 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:56 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 17:59:57 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 17:59:57 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=13
max_threads=151
threads_connected=12
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e896f8
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=0x4474c07c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x83e5898 _ZN5Error15assertionFailedEPKci + 32
0x84093ba _ZN6RecordD2Ev + 42
0x840ad6d _ZN13RecordVersionD0Ev + 71
0x8409f4f _ZN6Record7releaseEv + 71
0x83c14d5 _ZN11Transaction13commitRecordsEv + 117
0x83c1f95 _ZN11Transaction17releaseDependencyEv + 183
0x83c144b _ZN11Transaction19releaseDependenciesEv + 193
0x83c06af _ZN11Transaction6commitEv + 619
0x83d1c2e _ZN10Connection6commitEv + 166
0x83ac3a0 _ZN17StorageConnection6commitEv + 100
0x83a6f64 _ZN16StorageInterface6commitEP10handlertonP3THDb + 134
0x82f8970 _Z19ha_commit_one_phaseP3THDb + 162
0x82f882d _Z15ha_commit_transP3THDb + 911
0x821958c _Z16end_active_transP3THD + 342
0x8219654 _Z11begin_transP3THD + 106
0x82215ee _Z21mysql_execute_commandP3THD + 20646
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8eb5260 = start transaction
thd->thread_id=545
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.

Number of processes running now: 0
070726 17:59:58  mysqld restarted
070726 17:59:58  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 17:59:58  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 17:59:58  InnoDB: Started; log sequence number 0 46409
070726 17:59:58 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:00 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e880a8
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=0x42d766ec, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x83e5898 _ZN5Error15assertionFailedEPKci + 32
0x8418e52 _ZN7Section14findNextRecordEiiP6Stream + 522
0x8418ed3 _ZN7Section14findNextRecordEiiP6Stream + 651
0x8418c45 _ZN7Section14findNextRecordEiP6Stream + 41
0x83ded09 _ZN3Dbb14findNextRecordEP7SectioniP6Stream + 31
0x83b7c5e _ZN5Table9fetchNextEi + 624
0x83ad15d _ZN15StorageDatabase7nextRowEP12StorageTableib + 81
0x83b1662 _ZN12StorageTable4nextEib + 46
0x83a5794 _ZN16StorageInterface8rnd_nextEPh + 140
0x82f3b7e _Z13rr_sequentialP14st_read_record + 130
0x827fb77 _Z10sub_selectP4JOINP13st_join_tableb + 223
0x827f6b0 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 756
0x826e6dd _ZN4JOIN4execEv + 7045
0x826ec3e _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel + 638
0x826983d _Z13handle_selectP3THDP6st_lexP13select_resultm + 365
0x8223fda _Z21execute_sqlcom_selectP3THDP13st_table_list + 772
0x821cb73 _Z21mysql_execute_commandP3THD + 1579
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ec98a0 = select * from t3 where data like '%'
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.
Serial Log possible gap: 4051 - 427

Number of processes running now: 0
070726 18:00:00  mysqld restarted
070726 18:00:00  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:00  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:00  InnoDB: Started; log sequence number 0 46409
070726 18:00:00 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Record has changed since last read in table 't4'
070726 18:00:01 [ERROR] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: Sort aborted
070726 18:00:01 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=11
max_threads=151
threads_connected=11
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e6b2f8
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=0x42d45f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ec8550 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4118 - 499

Number of processes running now: 0
070726 18:00:01  mysqld restarted
070726 18:00:01  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:01  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:01  InnoDB: Started; log sequence number 0 46409
070726 18:00:01 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:02 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e880a8
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=0x42d766ec, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x83e5898 _ZN5Error15assertionFailedEPKci + 32
0x8418e52 _ZN7Section14findNextRecordEiiP6Stream + 522
0x8418ed3 _ZN7Section14findNextRecordEiiP6Stream + 651
0x8418c45 _ZN7Section14findNextRecordEiP6Stream + 41
0x83ded09 _ZN3Dbb14findNextRecordEP7SectioniP6Stream + 31
0x83b7c5e _ZN5Table9fetchNextEi + 624
0x83ad15d _ZN15StorageDatabase7nextRowEP12StorageTableib + 81
0x83b1662 _ZN12StorageTable4nextEib + 46
0x83a5794 _ZN16StorageInterface8rnd_nextEPh + 140
0x82f3b7e _Z13rr_sequentialP14st_read_record + 130
0x827fb77 _Z10sub_selectP4JOINP13st_join_tableb + 223
0x827f6b0 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 756
0x826e6dd _ZN4JOIN4execEv + 7045
0x826ec3e _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel + 638
0x826983d _Z13handle_selectP3THDP6st_lexP13select_resultm + 365
0x8223fda _Z21execute_sqlcom_selectP3THDP13st_table_list + 772
0x821cb73 _Z21mysql_execute_commandP3THD + 1579
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ec98a0 = select count(*) from t1,t2,t3 where t1.id=t2.id and t2.id=t3.id
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.
Serial Log possible gap: 4123 - 504

Number of processes running now: 0
070726 18:00:02  mysqld restarted
070726 18:00:02  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:02  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:02  InnoDB: Started; log sequence number 0 46409
070726 18:00:02 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:02 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e8dba8
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=0x42da7f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed0978 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4134 - 515
Fatal signal 11 while backtracing

Number of processes running now: 0
070726 18:00:02  mysqld restarted
070726 18:00:03  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:03  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:03  InnoDB: Started; log sequence number 0 46409
070726 18:00:03 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:03 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e88088
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=0x42f2df4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ec9880 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
Fatal signal 11 while backtracing
Serial Log possible gap: 4135 - 516
Fatal signal 6 while backtracing

Number of processes running now: 0
070726 18:00:03  mysqld restarted
070726 18:00:03  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:03  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:03  InnoDB: Started; log sequence number 0 46409
070726 18:00:03 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:03 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e8dba0
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=0x42da7f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed0970 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4136 - 517

Number of processes running now: 0
070726 18:00:03  mysqld restarted
070726 18:00:04  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:04  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:04  InnoDB: Started; log sequence number 0 46409
070726 18:00:04 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:04 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8ea5a58
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=0x42e6bf4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ef2990 = insert ignore into t3(data) values (concat(@name,@birthdate))
thd->thread_id=8
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.
mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
Serial Log possible gap: 4141 - 522
Fatal signal 6 while backtracing
mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.

Number of processes running now: 0
070726 18:00:04  mysqld restarted
070726 18:00:04  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:04  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:04  InnoDB: Started; log sequence number 0 46409
070726 18:00:04 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:05 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e58e68
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=0x42d14f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ebb7d8 = insert ignore into t3(data) values (concat(@name,@birthdate))
thd->thread_id=1
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.
Serial Log possible gap: 4149 - 530

Number of processes running now: 0
070726 18:00:05  mysqld restarted
070726 18:00:05  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:05  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:05  InnoDB: Started; log sequence number 0 46409
070726 18:00:05 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:05 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8eadea8
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=0x42e09f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed6e80 = insert ignore into t3(data) values (concat(@name,@birthdate))
thd->thread_id=6
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.
Serial Log possible gap: 4152 - 533

Number of processes running now: 0
070726 18:00:05  mysqld restarted
070726 18:00:06  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:06  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:06  InnoDB: Started; log sequence number 0 46409
070726 18:00:06 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:06 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e880a8
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=0x42d76f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed1910 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4153 - 534
Fatal signal 11 while backtracing

Number of processes running now: 0
070726 18:00:06  mysqld restarted
070726 18:00:06  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:06  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:06  InnoDB: Started; log sequence number 0 46409
070726 18:00:06 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:06 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e880a8
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=0x42d76f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed0e48 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4154 - 535
Fatal signal 11 while backtracing

Number of processes running now: 0
070726 18:00:06  mysqld restarted
070726 18:00:07  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:07  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:07  InnoDB: Started; log sequence number 0 46409
070726 18:00:07 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:07 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e8dba0
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=0x42da7f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed0a88 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4155 - 536
Fatal signal 11 while backtracing

Number of processes running now: 0
070726 18:00:07  mysqld restarted
070726 18:00:07  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:07  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:07  InnoDB: Started; log sequence number 0 46409
070726 18:00:07 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:07 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e8dba8
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=0x42da7f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed0978 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4156 - 537

Number of processes running now: 0
070726 18:00:07  mysqld restarted
070726 18:00:08  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:08  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:08  InnoDB: Started; log sequence number 0 46409
070726 18:00:08 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:08 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e99898
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=0x42e09f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ee8990 = insert ignore into t3(data) values (concat(@name,@birthdate))
thd->thread_id=6
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.
Serial Log possible gap: 4159 - 540

Number of processes running now: 0
070726 18:00:08  mysqld restarted
070726 18:00:08  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:08  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:08  InnoDB: Started; log sequence number 0 46409
070726 18:00:08 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
070726 18:00:09 - mysqld got signal 4;
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=8388572
read_buffer_size=131072
max_used_connections=10
max_threads=151
threads_connected=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337602 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e8dba8
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=0x42da7f4c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x821009b handle_segfault + 541
0xffffe410 _end + -142800224
0x83e58b2 _ZN5Error10debugBreakEv + 18
0x83e582a _ZN5Error5errorEPKcz + 82
0x8448e29 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 585
0x83de6d7 _ZN3Dbb9fetchPageEi8PageType8LockType + 51
0x83de7ff _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x8417bad _ZN7Section10insertStubEj + 471
0x83de904 _ZN3Dbb10insertStubEP7SectionP11Transaction + 36
0x83bc81c _ZN5Table6insertEP11TransactionP6Stream + 286
0x83ad109 _ZN15StorageDatabase6insertEP10ConnectionP5TableP6Stream + 39
0x83b14d7 _ZN12StorageTable6insertEv + 59
0x83a6acf _ZN16StorageInterface9write_rowEPh + 253
0x82fe365 _ZN7handler12ha_write_rowEPh + 33
0x828eaeb _Z12write_recordP3THDP8st_tableP12st_copy_info + 1851
0x828d465 _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 2275
0x821ef90 _Z21mysql_execute_commandP3THD + 10824
0x82259e1 _Z11mysql_parseP3THDPKcjPS2_ + 339
0x821b02d _Z16dispatch_command19enum_server_commandP3THDPcj + 2325
0x821a70c _Z10do_commandP3THD + 612
0x8219273 handle_one_connection + 253
0x40250aa7 _end + 933376311
0x401e6c2e _end + 932942526
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 0x8ed7a48 = insert ignore into t3(data) values (concat(@name,@birthdate))
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.
Serial Log possible gap: 4161 - 542

Number of processes running now: 0
070726 18:00:09  mysqld restarted
070726 18:00:09  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070726 18:00:09  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 46409.
InnoDB: Doing recovery: scanned up to log sequence number 0 46409
070726 18:00:09  InnoDB: Started; log sequence number 0 46409
070726 18:00:09 [Note] /home/sbester/server/6.0/mysql-6.0.2-alpha-linux-i686/bin/mysqld: ready for connections.
Version: '6.0.2-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes