Description:
merge.test fails when compiled with the default options on windows xp (32 bit) using vs 2008. Note that I'm running using strawberry perl and the gnuwin32 tools (and not cygwin) :
main.merge [ fail ]
Test ended at 2010-02-08 16:31:48
CURRENT_TEST: main.merge
mysqltest: At line 1182: query 'REPAIR TABLE t2' failed: 2013: Lost connection
o MySQL server during query
The result from queries just before the failure was:
< snip >
#
# Repair
#
REPAIR TABLE t4;
Table Op Msg_type Msg_text
test.t4 repair note The storage engine for the table doesn't support repair
REPAIR TABLE t2;
Table Op Msg_type Msg_text
test.t2 repair status OK
SELECT * FROM t4 ORDER BY c1;
c1
1
2
3
4
4
LOCK TABLES t3 WRITE, t2 WRITE, t4 WRITE, t1 WRITE;
REPAIR TABLE t4;
Table Op Msg_type Msg_text
test.t4 repair note The storage engine for the table doesn't support repair
More results from queries before failure can be found in Z:\test-win-5.1-bugtea
\mysql-test\var\log\merge.log
Server [mysqld.1 - pid: 3208, winpid: 3208, exit: 0] failed during test run
Server log from this test:
100208 17:31:22 [Warning] The syntax '--default-character-set' is deprecated an
will be removed in a future release. Please use --character-set-server instead
100208 17:31:22 [Warning] Z:/test-win-5.1-bugteam/sql/mysqld.exe: unknown varia
le 'loose-innodb_data_file_path=ibdata1:10M:autoextend'
100208 17:31:22 [Warning] Z:/test-win-5.1-bugteam/sql/mysqld.exe: unknown optio
'--loose-skip-innodb'
100208 17:31:22 [Note] Event Scheduler: Loaded 0 events
100208 17:31:22 [Note] Z:/test-win-5.1-bugteam/sql/mysqld.exe: ready for connec
ions.
Version: '5.1.45-debug-log' socket: '' port: 13000 Source distribution
100208 17:31:24 [ERROR] Got error 124 when reading table '.\test\t1'
100208 17:31:38 [Note] Retrying repair of: '.\test\t2' with keycache
Assertion failed: fd != -1, file Z:\test-win-5.1-bugteam\mysys\my_seek.c, line
8
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
100208 17:31:38 - mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
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 = 59964 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x1205600
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...
00444A93 mysqld.exe!my_sigabrt_handler()[mysqld.cc:2047]
004092EB mysqld.exe!raise()[winsig.c:590]
00411855 mysqld.exe!abort()[abort.c:71]
007EAAF7 mysqld.exe!_wassert()[assert.c:346]
0082056D mysqld.exe!my_seek()[my_seek.c:58]
0081D29E mysqld.exe!init_io_cache()[mf_iocache.c:209]
007ABB25 mysqld.exe!mi_repair()[mi_check.c:1559]
0078B4F6 mysqld.exe!ha_myisam::repair()[ha_myisam.cc:1156]
0078AC7A mysqld.exe!ha_myisam::repair()[ha_myisam.cc:1031]
004E257A mysqld.exe!handler::ha_repair()[handler.cc:3154]
00578240 mysqld.exe!mysql_admin_table()[sql_table.cc:4780]
0057985F mysqld.exe!mysql_repair_table()[sql_table.cc:5046]
005AF5B4 mysqld.exe!mysql_execute_command()[sql_parse.cc:2983]
005B7C18 mysqld.exe!mysql_parse()[sql_parse.cc:5971]
005ABABC mysqld.exe!dispatch_command()[sql_parse.cc:1233]
005AB0D2 mysqld.exe!do_command()[sql_parse.cc:874]
004A5FF8 mysqld.exe!handle_one_connection()[sql_connect.cc:1127]
0080C7B6 mysqld.exe!pthread_start()[my_winthread.c:85]
007EDAF3 mysqld.exe!_callthreadstart()[thread.c:293]
007EDA89 mysqld.exe!_threadstart()[thread.c:277]
7C80B729 kernel32.dll!GetModuleFileNameA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0121B0F0=REPAIR TABLE t2
thd->thread_id=2
thd->killed=NOT_KILLED
How to repeat:
win/configure.js
win/build-nmake.bat
perl mysql-test-run.pl --force merge
using strawberry perl, gnuwin32 bison and diff from the cmd command line
Description: merge.test fails when compiled with the default options on windows xp (32 bit) using vs 2008. Note that I'm running using strawberry perl and the gnuwin32 tools (and not cygwin) : main.merge [ fail ] Test ended at 2010-02-08 16:31:48 CURRENT_TEST: main.merge mysqltest: At line 1182: query 'REPAIR TABLE t2' failed: 2013: Lost connection o MySQL server during query The result from queries just before the failure was: < snip > # # Repair # REPAIR TABLE t4; Table Op Msg_type Msg_text test.t4 repair note The storage engine for the table doesn't support repair REPAIR TABLE t2; Table Op Msg_type Msg_text test.t2 repair status OK SELECT * FROM t4 ORDER BY c1; c1 1 2 3 4 4 LOCK TABLES t3 WRITE, t2 WRITE, t4 WRITE, t1 WRITE; REPAIR TABLE t4; Table Op Msg_type Msg_text test.t4 repair note The storage engine for the table doesn't support repair More results from queries before failure can be found in Z:\test-win-5.1-bugtea \mysql-test\var\log\merge.log Server [mysqld.1 - pid: 3208, winpid: 3208, exit: 0] failed during test run Server log from this test: 100208 17:31:22 [Warning] The syntax '--default-character-set' is deprecated an will be removed in a future release. Please use --character-set-server instead 100208 17:31:22 [Warning] Z:/test-win-5.1-bugteam/sql/mysqld.exe: unknown varia le 'loose-innodb_data_file_path=ibdata1:10M:autoextend' 100208 17:31:22 [Warning] Z:/test-win-5.1-bugteam/sql/mysqld.exe: unknown optio '--loose-skip-innodb' 100208 17:31:22 [Note] Event Scheduler: Loaded 0 events 100208 17:31:22 [Note] Z:/test-win-5.1-bugteam/sql/mysqld.exe: ready for connec ions. Version: '5.1.45-debug-log' socket: '' port: 13000 Source distribution 100208 17:31:24 [ERROR] Got error 124 when reading table '.\test\t1' 100208 17:31:38 [Note] Retrying repair of: '.\test\t2' with keycache Assertion failed: fd != -1, file Z:\test-win-5.1-bugteam\mysys\my_seek.c, line 8 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. 100208 17:31:38 - mysqld got exception 0x80000003 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=3 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 = 59964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x1205600 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... 00444A93 mysqld.exe!my_sigabrt_handler()[mysqld.cc:2047] 004092EB mysqld.exe!raise()[winsig.c:590] 00411855 mysqld.exe!abort()[abort.c:71] 007EAAF7 mysqld.exe!_wassert()[assert.c:346] 0082056D mysqld.exe!my_seek()[my_seek.c:58] 0081D29E mysqld.exe!init_io_cache()[mf_iocache.c:209] 007ABB25 mysqld.exe!mi_repair()[mi_check.c:1559] 0078B4F6 mysqld.exe!ha_myisam::repair()[ha_myisam.cc:1156] 0078AC7A mysqld.exe!ha_myisam::repair()[ha_myisam.cc:1031] 004E257A mysqld.exe!handler::ha_repair()[handler.cc:3154] 00578240 mysqld.exe!mysql_admin_table()[sql_table.cc:4780] 0057985F mysqld.exe!mysql_repair_table()[sql_table.cc:5046] 005AF5B4 mysqld.exe!mysql_execute_command()[sql_parse.cc:2983] 005B7C18 mysqld.exe!mysql_parse()[sql_parse.cc:5971] 005ABABC mysqld.exe!dispatch_command()[sql_parse.cc:1233] 005AB0D2 mysqld.exe!do_command()[sql_parse.cc:874] 004A5FF8 mysqld.exe!handle_one_connection()[sql_connect.cc:1127] 0080C7B6 mysqld.exe!pthread_start()[my_winthread.c:85] 007EDAF3 mysqld.exe!_callthreadstart()[thread.c:293] 007EDA89 mysqld.exe!_threadstart()[thread.c:277] 7C80B729 kernel32.dll!GetModuleFileNameA() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0121B0F0=REPAIR TABLE t2 thd->thread_id=2 thd->killed=NOT_KILLED How to repeat: win/configure.js win/build-nmake.bat perl mysql-test-run.pl --force merge using strawberry perl, gnuwin32 bison and diff from the cmd command line