thd: 0x35a8040
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...
00923CC8    mysqld-debug.exe!my_strtod()[strtod.c:101]
0092D03F    mysqld-debug.exe!my_strntod_8bit()[ctype-simple.c:831]
0060E560    mysqld-debug.exe!Field_blob::val_real()[field.cc:7785]
00595D79    mysqld-debug.exe!Item_field::val_real()[item.cc:2039]
00590DBB    mysqld-debug.exe!Item::val_bool()[item.cc:195]
0048652B    mysqld-debug.exe!Item_func_not::val_int()[item_cmpfunc.cc:287]
0064FD68    mysqld-debug.exe!join_read_const_table()[sql_select.cc:11798]
0063A599    mysqld-debug.exe!make_join_statistics()[sql_select.cc:2788]
006345D5    mysqld-debug.exe!JOIN::optimize()[sql_select.cc:1021]
006398EE    mysqld-debug.exe!mysql_select()[sql_select.cc:2503]
0065EB58    mysqld-debug.exe!mysql_explain_union()[sql_select.cc:16834]
005B8FF3    mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5071]
005B15D1    mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2287]
005BB54F    mysqld-debug.exe!mysql_parse()[sql_parse.cc:6017]
005AF205    mysqld-debug.exe!dispatch_command()[sql_parse.cc:1254]
005AE7B2    mysqld-debug.exe!do_command()[sql_parse.cc:882]
004A8678    mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1136]
008E5A16    mysqld-debug.exe!pthread_start()[my_winthread.c:85]
008C1811    mysqld-debug.exe!_callthreadstart()[thread.c:293]
008C17B7    mysqld-debug.exe!_threadstart()[thread.c:277]
7D4DFE37    kernel32.dll!FlsSetValue()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0351D4C8=explain partitions
select   count(*) from
        `test`.`t19` as `t19` use index (idx53)
         left join `test`.`t24` as `t24`
on (!t19.col44 )


group by
        t19.col44



order by
        t24.col65,
        t19.col45
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.

H:\mysql\5.1\5.1.49\mysql-advanced-gpl-5.1.49-win32\bin>mysqld-debug --no-defaults --console --skip-gr --s
100809  8:53:22 [Note] Plugin 'FEDERATED' is disabled.
100809  8:53:22  InnoDB: Error: page 232 log sequence number 0 156059960
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:22  InnoDB: Error: page 407 log sequence number 0 157164661
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:22  InnoDB: Error: page 410 log sequence number 0 102663973
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:22  InnoDB: Started; log sequence number 0 5179093
InnoDB: !!! innodb_force_recovery is set to 4 !!!
100809  8:53:22 [Note] mysqld-debug: ready for connections.
Version: '5.1.49-enterprise-gpl-advanced-debug'  socket: ''  port: 3306  MySQL Enterprise Server - Advance
100809  8:53:22  InnoDB: Error: page 60 log sequence number 0 156141166
InnoDB: is in the future! Current system log sequence number 0 5179103.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:22 - mysqld got exception 0xc0000005 ;
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=8384512
read_buffer_size=131072
max_used_connections=2
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 = 337724 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x354d358
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...
0074A3EC    mysqld-debug.exe!Geometry::create_from_wkb()[spatial.cc:248]
006D32DD    mysqld-debug.exe!Item_func_geometry_from_wkb::val_str()[item_geofunc.cc:107]
006278F8    mysqld-debug.exe!Item_str_func::val_real()[item_strfunc.cc:95]
00590DBB    mysqld-debug.exe!Item::val_bool()[item.cc:195]
00493824    mysqld-debug.exe!Item_cond_or::val_int()[item_cmpfunc.cc:4425]
0064FD68    mysqld-debug.exe!join_read_const_table()[sql_select.cc:11798]
0063A599    mysqld-debug.exe!make_join_statistics()[sql_select.cc:2788]
006345D5    mysqld-debug.exe!JOIN::optimize()[sql_select.cc:1021]
006398EE    mysqld-debug.exe!mysql_select()[sql_select.cc:2503]
0065EB58    mysqld-debug.exe!mysql_explain_union()[sql_select.cc:16834]
005B8FF3    mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5071]
005B15D1    mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2287]
005BB54F    mysqld-debug.exe!mysql_parse()[sql_parse.cc:6017]
005AF205    mysqld-debug.exe!dispatch_command()[sql_parse.cc:1254]
005AE7B2    mysqld-debug.exe!do_command()[sql_parse.cc:882]
004A8678    mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1136]
008E5A16    mysqld-debug.exe!pthread_start()[my_winthread.c:85]
008C1811    mysqld-debug.exe!_callthreadstart()[thread.c:293]
008C17B7    mysqld-debug.exe!_threadstart()[thread.c:277]
7D4DFE37    kernel32.dll!FlsSetValue()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 035472C8=explain
select
`t2`.`a2` as a2
from
        `test`.`t2` as `t2`
         left outer join `test`.`t7` as `t7`
on (linestringfromwkb((t2.col3)) || @var2:=(case when (t7.col17) then (t7.col17) else (t7.a7) end) )
thd->thread_id=3
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.

H:\mysql\5.1\5.1.49\mysql-advanced-gpl-5.1.49-win32\bin>mysqld-debug --no-defaults --console --skip-gr --s
100809  8:53:24 [Note] Plugin 'FEDERATED' is disabled.
100809  8:53:24  InnoDB: Error: page 232 log sequence number 0 156059960
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:24  InnoDB: Error: page 407 log sequence number 0 157164661
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:24  InnoDB: Error: page 410 log sequence number 0 102663973
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:24  InnoDB: Started; log sequence number 0 5179093
InnoDB: !!! innodb_force_recovery is set to 4 !!!
100809  8:53:24 [Note] mysqld-debug: ready for connections.
Version: '5.1.49-enterprise-gpl-advanced-debug'  socket: ''  port: 3306  MySQL Enterprise Server - Advance
100809  8:53:25  InnoDB: Error: page 460 log sequence number 0 155780301
InnoDB: is in the future! Current system log sequence number 0 5179103.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:25  InnoDB: Error: page 533 log sequence number 0 155969304
InnoDB: is in the future! Current system log sequence number 0 5179103.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:25  InnoDB: Error: page 60 log sequence number 0 156141166
InnoDB: is in the future! Current system log sequence number 0 5179103.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:25 - mysqld got exception 0xc0000005 ;
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=8384512
read_buffer_size=131072
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 = 337724 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x352c4e8
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...
006D438B    mysqld-debug.exe!Item_func_spatial_collection::val_str()[item_geofunc.cc:434]
00627A6C    mysqld-debug.exe!Item_str_func::val_int()[item_strfunc.cc:107]
004928EF    mysqld-debug.exe!Item_func_bit_and::val_int()[item_cmpfunc.cc:4067]
0064FD68    mysqld-debug.exe!join_read_const_table()[sql_select.cc:11798]
0063A599    mysqld-debug.exe!make_join_statistics()[sql_select.cc:2788]
006345D5    mysqld-debug.exe!JOIN::optimize()[sql_select.cc:1021]
006398EE    mysqld-debug.exe!mysql_select()[sql_select.cc:2503]
0065EB58    mysqld-debug.exe!mysql_explain_union()[sql_select.cc:16834]
005B8FF3    mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5071]
005B15D1    mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2287]
005BB54F    mysqld-debug.exe!mysql_parse()[sql_parse.cc:6017]
005AF205    mysqld-debug.exe!dispatch_command()[sql_parse.cc:1254]
005AE7B2    mysqld-debug.exe!do_command()[sql_parse.cc:882]
004A8678    mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1136]
008E5A16    mysqld-debug.exe!pthread_start()[my_winthread.c:85]
008C1811    mysqld-debug.exe!_callthreadstart()[thread.c:293]
008C17B7    mysqld-debug.exe!_threadstart()[thread.c:277]
7D4DFE37    kernel32.dll!FlsSetValue()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 035472C8=explain partitions
select
`t2`.`a2` as a2
from
        `test`.`t7` as `t7`
         right outer join `test`.`t2` as `t2`
on (char((t7.col17) using macroman) & multipoint((t2.col3),(t2.col2),(t2.col2),(t2.a2),(t2.col3)) )
  where
 row(t2.a2 ,t7.col17 ,t7.col17 )<=> row( t7.a7 , t7.a7 , t2.a2 )xor
 row(t2.col3  collate ucs2_spanish_ci ,t2.a2 )<> row(( select '1' ) ,( select '1' ) )or
t2.col2  collate utf8_general_ci <= t7.a7
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.

H:\mysql\5.1\5.1.49\mysql-advanced-gpl-5.1.49-win32\bin>
H:\mysql\5.1\5.1.49\mysql-advanced-gpl-5.1.49-win32\bin>mysqld-debug --no-defaults --console --skip-gr --s
100809  8:53:27 [Note] Plugin 'FEDERATED' is disabled.
100809  8:53:27  InnoDB: Error: page 232 log sequence number 0 156059960
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:27  InnoDB: Error: page 407 log sequence number 0 157164661
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:27  InnoDB: Error: page 410 log sequence number 0 102663973
InnoDB: is in the future! Current system log sequence number 0 5179093.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:27  InnoDB: Started; log sequence number 0 5179093
InnoDB: !!! innodb_force_recovery is set to 4 !!!
100809  8:53:27 [Note] mysqld-debug: ready for connections.
Version: '5.1.49-enterprise-gpl-advanced-debug'  socket: ''  port: 3306  MySQL Enterprise Server - Advance
100809  8:53:28  InnoDB: Error: page 419 log sequence number 0 155411701
InnoDB: is in the future! Current system log sequence number 0 5179103.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100809  8:53:28 - mysqld got exception 0xc0000005 ;
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=8384512
read_buffer_size=131072
max_used_connections=2
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 = 337724 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x351d4b8
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...
00923CC8    mysqld-debug.exe!my_strtod()[strtod.c:101]
0092D03F    mysqld-debug.exe!my_strntod_8bit()[ctype-simple.c:831]
0060E560    mysqld-debug.exe!Field_blob::val_real()[field.cc:7785]
00595D79    mysqld-debug.exe!Item_field::val_real()[item.cc:2039]
0048C6B3    mysqld-debug.exe!Item_func_between::val_int()[item_cmpfunc.cc:2331]
00510B5D    mysqld-debug.exe!Item_int_func::val_real()[item_func.cc:618]
005135ED    mysqld-debug.exe!Item_func_div::real_op()[item_func.cc:1261]
00511688    mysqld-debug.exe!Item_func_numhybrid::val_real()[item_func.cc:795]
0051D572    mysqld-debug.exe!Item_func_set_user_var::check()[item_func.cc:4077]
0051DD8B    mysqld-debug.exe!Item_func_set_user_var::val_int()[item_func.cc:4226]
0064FD68    mysqld-debug.exe!join_read_const_table()[sql_select.cc:11798]
0063A599    mysqld-debug.exe!make_join_statistics()[sql_select.cc:2788]
006345D5    mysqld-debug.exe!JOIN::optimize()[sql_select.cc:1021]
006398EE    mysqld-debug.exe!mysql_select()[sql_select.cc:2503]
0065EB58    mysqld-debug.exe!mysql_explain_union()[sql_select.cc:16834]
005B8FF3    mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5071]
005B15D1    mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2287]
005BB54F    mysqld-debug.exe!mysql_parse()[sql_parse.cc:6017]
005AF205    mysqld-debug.exe!dispatch_command()[sql_parse.cc:1254]
005AE7B2    mysqld-debug.exe!do_command()[sql_parse.cc:882]
004A8678    mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1136]
008E5A16    mysqld-debug.exe!pthread_start()[my_winthread.c:85]
008C1811    mysqld-debug.exe!_callthreadstart()[thread.c:293]
008C17B7    mysqld-debug.exe!_threadstart()[thread.c:277]
7D4DFE37    kernel32.dll!FlsSetValue()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0354B318=explain
select   count(*) from
        `test`.`t15` as `t15`
         left outer join `test`.`t12` as `t12` use index (idx34)
on (@var5:=((t15.a15) between (t15.col33) and (t15.col34)) / @var0 )
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.

H:\mysql\5.1\5.1.49\mysql-advanced-gpl-5.1.49-win32\bin>mysqld-debug --no-defaults --console --skip-gr --s