090611 17:33:23 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
090611 17:33:23 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:33:23 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
090611 17:33:23  InnoDB: Started; log sequence number 0 2116514
090611 17:33:23 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:33:23 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:33:23 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:33:24 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:33:24 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:33:25 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:33:26 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:33:26 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:33:27 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:33:27 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './fedora9-relay-bin.000001' position: 4
090611 17:33:27 [Note] Event Scheduler: Loaded 0 events
090611 17:33:27 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
090611 17:33:27 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'FIRST' at position 4
090611 17:33:58 [Note] Slave I/O thread killed while reading event
090611 17:33:58 [Note] Slave I/O thread exiting, read up to log 'fedora9-bin.000001', position 106
090611 17:33:58 [Note] Error reading relay log event: slave SQL thread was killed
090611 17:33:58 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './fedora9-relay-bin.000001' position: 4
090611 17:33:58 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'FIRST' at position 4
090611 17:35:49 [Warning] Statement is not safe to log in statement format. Statement: INSERT INTO billing_setfinlevel (`date`, account_id, fin_level, success) VALUES (NOW(),  NAME_CONST('_account_id',_latin1'1069' COLLATE 'latin1_swedish_ci'),  NAME_CONST('_fin_level',_latin1'3' COLLATE 'latin1_swedish_ci'), ROW_COUNT())
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0x110400]
/opt/lampp/sbin/mysqld(_ZN14Arg_comparator12set_cmp_funcEP15Item_bool_func2PP4ItemS4_11Item_result+0x44)[0x8163014]
/opt/lampp/sbin/mysqld(_ZN15Item_bool_func218fix_length_and_decEv+0x124)[0x81662c4]
/opt/lampp/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a5)[0x814c435]
/opt/lampp/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTS2_PP4Item+0x1f1)[0x8222551]
/opt/lampp/sbin/mysqld(_Z20mysql_prepare_deleteP3THDP10TABLE_LISTPP4Item+0xe1)[0x826f011]
/opt/lampp/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb+0xb1)[0x826f781]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x33d8)[0x81e75d8]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x3b3)[0x829a5d3]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_info+0x26)[0x829adc6]
/opt/lampp/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_infob+0x11c)[0x8309d3c]
/opt/lampp/sbin/mysqld(handle_slave_sql+0x7ae)[0x830f32e]
/lib/libpthread.so.0[0x78632f]
/lib/libc.so.6(clone+0x5e)[0x6a327e]
090611 17:38:59 - 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=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=151
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8e594e0
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...
stack_bottom = 0x48d3a4 thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8ec6e0b = DELETE
FROM
  sessions
WHERE
  start_time >  NAME_CONST('_clean_date',_binary'2009-06-11 13:44:11' COLLATE 'binary')
thd->thread_id=5
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090611 17:39:00 mysqld_safe Number of processes running now: 0
090611 17:39:00 mysqld_safe mysqld restarted
090611 17:39:00 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:39:00 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090611 17:39: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...
InnoDB: Last MySQL binlog file position 0 106, file name ./fedora9-bin.000001
090611 17:39:00  InnoDB: Started; log sequence number 0 2121831
090611 17:39:00 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:39:00 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:39:00 [Note] The server was not shutdown correctly, recovery required
090611 17:39:00 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:39:00 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:39:01 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:39:02 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:39:02 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:39:03 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:39:03 [Note] Recovering after a crash using fedora9-bin
090611 17:39:03 [Note] Starting crash recovery...
090611 17:39:03 [Note] Crash recovery finished.
090611 17:39:03 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:39:04 [Note] Slave SQL thread initialized, starting replication in log 'fedora9-bin.000001' at position 9361, relay log './fedora9-relay-bin.000003' position: 9508
090611 17:39:04 [Note] Event Scheduler: Loaded 0 events
090611 17:39:04 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
090611 17:39:04 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'fedora9-bin.000001' at position 9560
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0x110400]
/opt/lampp/sbin/mysqld(_ZN14Arg_comparator12set_cmp_funcEP15Item_bool_func2PP4ItemS4_11Item_result+0x44)[0x8163014]
/opt/lampp/sbin/mysqld(_ZN15Item_bool_func218fix_length_and_decEv+0x124)[0x81662c4]
/opt/lampp/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a5)[0x814c435]
/opt/lampp/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTS2_PP4Item+0x1f1)[0x8222551]
/opt/lampp/sbin/mysqld(_Z20mysql_prepare_deleteP3THDP10TABLE_LISTPP4Item+0xe1)[0x826f011]
/opt/lampp/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb+0xb1)[0x826f781]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x33d8)[0x81e75d8]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x3b3)[0x829a5d3]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_info+0x26)[0x829adc6]
/opt/lampp/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_infob+0x11c)[0x8309d3c]
/opt/lampp/sbin/mysqld(handle_slave_sql+0x7ae)[0x830f32e]
/lib/libpthread.so.0[0x78632f]
/lib/libc.so.6(clone+0x5e)[0x6a327e]
090611 17:39: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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8c144e0
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...
stack_bottom = 0x4be3a4 thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xac3005db is an invalid pointer
thd->thread_id=2
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090611 17:39:04 mysqld_safe Number of processes running now: 0
090611 17:39:04 mysqld_safe mysqld restarted
090611 17:39:04 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:39:04 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090611 17:39: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...
InnoDB: Last MySQL binlog file position 0 106, file name ./fedora9-bin.000001
090611 17:39:05  InnoDB: Started; log sequence number 0 2121870
090611 17:39:05 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:39:05 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:39:05 [Note] The server was not shutdown correctly, recovery required
090611 17:39:05 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:39:05 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:39:05 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:39:06 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:39:07 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:39:08 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:39:08 [Note] Recovering after a crash using fedora9-bin
090611 17:39:08 [Note] Starting crash recovery...
090611 17:39:08 [Note] Crash recovery finished.
090611 17:39:08 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:39:08 [Note] Slave SQL thread initialized, starting replication in log 'fedora9-bin.000001' at position 9361, relay log './fedora9-relay-bin.000003' position: 9508
090611 17:39:08 [Note] Event Scheduler: Loaded 0 events
090611 17:39:08 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0x110400]
/opt/lampp/sbin/mysqld(_ZN14Arg_comparator12set_cmp_funcEP15Item_bool_func2PP4ItemS4_11Item_result+0x44)[0x8163014]
/opt/lampp/sbin/mysqld(_ZN15Item_bool_func218fix_length_and_decEv+0x124)[0x81662c4]
/opt/lampp/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a5)[0x814c435]
/opt/lampp/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTS2_PP4Item+0x1f1)[0x8222551]
090611 17:39:08 - 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xacd00468
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...
stack_bottom = 0x4be3a4 thread_stack 0x30000
090611 17:39:08 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'fedora9-bin.000001' at position 9560
/opt/lampp/sbin/mysqld(_Z20mysql_prepare_deleteP3THDP10TABLE_LISTPP4Item+0xe1)[0x826f011]
/opt/lampp/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb+0xb1)[0x826f781]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x33d8)[0x81e75d8]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x3b3)[0x829a5d3]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_info+0x26)[0x829adc6]
/opt/lampp/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_infob+0x11c)[0x8309d3c]
/opt/lampp/sbin/mysqld(handle_slave_sql+0x7ae)[0x830f32e]
/lib/libpthread.so.0[0x78632f]
/lib/libc.so.6(clone+0x5e)[0x6a327e]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xacd0981b is an invalid pointer
thd->thread_id=2
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090611 17:39:09 mysqld_safe Number of processes running now: 0
090611 17:39:09 mysqld_safe mysqld restarted
090611 17:39:09 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:39:09 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090611 17:39: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...
InnoDB: Last MySQL binlog file position 0 106, file name ./fedora9-bin.000001
090611 17:39:09  InnoDB: Started; log sequence number 0 2121870
090611 17:39:09 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:39:09 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:39:09 [Note] The server was not shutdown correctly, recovery required
090611 17:39:09 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:39:09 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:39:10 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:39:11 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:39:11 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:39:12 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:39:12 [Note] Recovering after a crash using fedora9-bin
090611 17:39:12 [Note] Starting crash recovery...
090611 17:39:12 [Note] Crash recovery finished.
090611 17:39:13 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:39:13 [Note] Slave SQL thread initialized, starting replication in log 'fedora9-bin.000001' at position 9361, relay log './fedora9-relay-bin.000003' position: 9508
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0x110400]
/opt/lampp/sbin/mysqld(_ZN14Arg_comparator12set_cmp_funcEP15Item_bool_func2PP4ItemS4_11Item_result+0x44)[0x8163014]
090611 17:39:13 - 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xa35d950
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...
stack_bottom = 0x4be3a4 thread_stack 0x30000
090611 17:39:13 [Note] Event Scheduler: Loaded 0 events
090611 17:39:13 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
090611 17:39:13 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'fedora9-bin.000001' at position 9560
/opt/lampp/sbin/mysqld(_ZN15Item_bool_func218fix_length_and_decEv+0x124)[0x81662c4]
/opt/lampp/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a5)[0x814c435]
/opt/lampp/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTS2_PP4Item+0x1f1)[0x8222551]
/opt/lampp/sbin/mysqld(_Z20mysql_prepare_deleteP3THDP10TABLE_LISTPP4Item+0xe1)[0x826f011]
/opt/lampp/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb+0xb1)[0x826f781]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x33d8)[0x81e75d8]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x3b3)[0x829a5d3]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_info+0x26)[0x829adc6]
/opt/lampp/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_infob+0x11c)[0x8309d3c]
/opt/lampp/sbin/mysqld(handle_slave_sql+0x7ae)[0x830f32e]
/lib/libpthread.so.0[0x78632f]
/lib/libc.so.6(clone+0x5e)[0x6a327e]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa38813b = DELETE
FROM
  sessions
WHERE
  start_time >  NAME_CONST('_clean_date',_binary'2009-06-11 13:44:11' COLLATE 'binary')
thd->thread_id=2
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090611 17:39:13 mysqld_safe Number of processes running now: 0
090611 17:39:13 mysqld_safe mysqld restarted
090611 17:39:14 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:39:14 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090611 17:39:14  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...
InnoDB: Last MySQL binlog file position 0 106, file name ./fedora9-bin.000001
090611 17:39:14  InnoDB: Started; log sequence number 0 2121870
090611 17:39:14 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:39:14 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:39:14 [Note] The server was not shutdown correctly, recovery required
090611 17:39:14 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:39:14 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:39:15 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:39:15 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:39:16 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:39:17 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:39:17 [Note] Recovering after a crash using fedora9-bin
090611 17:39:17 [Note] Starting crash recovery...
090611 17:39:17 [Note] Crash recovery finished.
090611 17:39:17 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:39:17 [Note] Slave SQL thread initialized, starting replication in log 'fedora9-bin.000001' at position 9361, relay log './fedora9-relay-bin.000003' position: 9508
090611 17:39:17 [Note] Event Scheduler: Loaded 0 events
090611 17:39:17 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0x110400]
/opt/lampp/sbin/mysqld(_ZN14Arg_comparator12set_cmp_funcEP15Item_bool_func2PP4ItemS4_11Item_result+0x44)[0x8163014]
090611 17:39:17 - 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x9b0a950
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...
stack_bottom = 0x4be3a4 thread_stack 0x30000
090611 17:39:18 [Note] Slave I/O thread: connected to master 'replicator@192.168.100.252:3306',replication started in log 'fedora9-bin.000001' at position 9560
/opt/lampp/sbin/mysqld(_ZN15Item_bool_func218fix_length_and_decEv+0x124)[0x81662c4]
/opt/lampp/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a5)[0x814c435]
/opt/lampp/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTS2_PP4Item+0x1f1)[0x8222551]
/opt/lampp/sbin/mysqld(_Z20mysql_prepare_deleteP3THDP10TABLE_LISTPP4Item+0xe1)[0x826f011]
/opt/lampp/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb+0xb1)[0x826f781]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x33d8)[0x81e75d8]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x3b3)[0x829a5d3]
/opt/lampp/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_info+0x26)[0x829adc6]
/opt/lampp/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_infob+0x11c)[0x8309d3c]
/opt/lampp/sbin/mysqld(handle_slave_sql+0x7ae)[0x830f32e]
/lib/libpthread.so.0[0x78632f]
/lib/libc.so.6(clone+0x5e)[0x6a327e]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9b3513b = DELETE
FROM
  sessions
WHERE
  start_time >  NAME_CONST('_clean_date',_binary'2009-06-11 13:44:11' COLLATE 'binary')
thd->thread_id=2
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
090611 17:39:18 mysqld_safe Number of processes running now: 0
090611 17:39:18 mysqld_safe mysqld restarted
090611 17:39:18 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
090611 17:39:18 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=fedora9-bin' to avoid this problem.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090611 17:39:18  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...
InnoDB: Last MySQL binlog file position 0 106, file name ./fedora9-bin.000001
090611 17:39:18  InnoDB: Started; log sequence number 0 2121870
090611 17:39:18 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
090611 17:39:18 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
090611 17:39:18 [Note] The server was not shutdown correctly, recovery required
090611 17:39:18 [Note] PBXT: Recovering from 1-43, bytes to read: 33554389
090611 17:39:18 [Note] PBXT:  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
090611 17:39:19 [Note] PBXT: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
090611 17:39:20 [Note] PBXT: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
090611 17:39:20 [Note] PBXT: 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
090611 17:39:21 [Note] PBXT: Recovering complete at 1-43, bytes read: 33554389
090611 17:39:21 [Note] Recovering after a crash using fedora9-bin
090611 17:39:21 [Note] Starting crash recovery...
090611 17:39:21 [Note] Crash recovery finished.
090611 17:39:21 [Note] /opt/lampp/sbin/mysqld: Normal shutdown

090611 17:39:22 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=fedora9-relay-bin' to avoid this problem.
090611 17:39:22 [Note] Slave I/O thread killed while connecting to master
090611 17:39:22 [Note] Slave I/O thread exiting, read up to log 'fedora9-bin.000001', position 9560
090611 17:39:22 [Note] Slave SQL thread initialized, starting replication in log 'fedora9-bin.000001' at position 9361, relay log './fedora9-relay-bin.000003' position: 9508
090611 17:39:22 [Note] Slave SQL thread exiting, replication stopped in log 'fedora9-bin.000001' at position 9361
090611 17:39:22 [Note] Event Scheduler: Loaded 0 events
090611 17:39:22 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
090611 17:39:22 [Note] Event Scheduler: Purging the queue. 0 events
090611 17:39:22 [Note] PrimeBase XT Engine shutdown...
090611 17:39:22  InnoDB: Starting shutdown...
090611 17:39:24  InnoDB: Shutdown completed; log sequence number 0 2121870
090611 17:39:24 [Note] /opt/lampp/sbin/mysqld: Shutdown complete

090611 17:39:24 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/fedora9.pid ended