Description:
jp.jp_convert_ujis w2 [ fail ]
Test ended at 2011-01-26 05:31:25
Server log is:
110126 7:31:24 [Note] Plugin 'FEDERATED' is disabled.
110126 5:31:24 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
110126 5:31:24 InnoDB: The InnoDB memory heap is disabled
110126 5:31:24 InnoDB: Mutexes and rw_locks use Windows interlocked functions
110126 5:31:24 InnoDB: Compressed tables use zlib 1.2.3
110126 5:31:24 InnoDB: Initializing buffer pool, size = 8.0M
110126 5:31:24 InnoDB: Completed initialization of buffer pool
110126 5:31:24 InnoDB: highest supported file format is Barracuda.
110126 5:31:24 InnoDB: Assertion failure in thread 6416 in file ..\..\..\mysql-5.6.2-m5\storage\innobase\buf\buf0buf.c line 2740
InnoDB: Failing assertion: block->page.offset == page_get_page_no(page_align(ptr))
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110126 7:31:24 - 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=1048576
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60653 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
000000013F6DD4A8 mysqld.exe!buf_block_align_instance()[buf0buf.c:2740]
000000013F6DD581 mysqld.exe!buf_block_align()[buf0buf.c:2769]
000000013F792207 mysqld.exe!mtr_memo_contains_page()[mtr0mtr.c:394]
000000013F792044 mysqld.exe!mtr_read_ulint()[mtr0mtr.c:370]
000000013F7C44D4 mysqld.exe!trx_undo_mem_create_at_db_start()[trx0undo.c:1293]
000000013F7C42B9 mysqld.exe!trx_undo_lists_init()[trx0undo.c:1418]
000000013F6C8911 mysqld.exe!trx_rseg_mem_create()[trx0rseg.c:202]
000000013F6C8DC4 mysqld.exe!trx_rseg_create_instance()[trx0rseg.c:276]
000000013F6C8C09 mysqld.exe!trx_rseg_list_and_array_init()[trx0rseg.c:341]
000000013F68B0EC mysqld.exe!trx_sys_init_at_db_start()[trx0sys.c:974]
000000013F669A95 mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1719]
000000013F625DA9 mysqld.exe!innobase_init()[ha_innodb.cc:2673]
000000013F1D9A16 mysqld.exe!ha_initialize_handlerton()[handler.cc:475]
000000013F1CFA69 mysqld.exe!plugin_initialize()[sql_plugin.cc:1063]
000000013F1CF792 mysqld.exe!plugin_init()[sql_plugin.cc:1344]
000000013F1B8772 mysqld.exe!init_server_components()[mysqld.cc:4114]
000000013F1B5961 mysqld.exe!win_main()[mysqld.cc:4675]
000000013F1B95F4 mysqld.exe!mysql_service()[mysqld.cc:4884]
000000013F1B9A52 mysqld.exe!mysqld_main()[mysqld.cc:5070]
000000013F1B1034 mysqld.exe!main()[main.cc:25]
000000013F96AEA7 mysqld.exe!__tmainCRTStartup()[crt0.c:266]
000000013F96ADAE mysqld.exe!mainCRTStartup()[crt0.c:182]
000000007751BE3D kernel32.dll!BaseThreadInitThunk()
0000000077656A51 ntdll.dll!RtlUserThreadStart()
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.
Writing a core file
Minidump written to Q:\pb2\test\sb_1-2883757-1295998435.4\mysql-5.6.2-m5-winx64\mysql-test\var-jp\2\mysqld.1\data\mysqld.dmp
How to repeat:
http://pb2.norway.sun.com/?template=mysql_show_test_failure&search=yes&push_id=1958184&tes...
Description: jp.jp_convert_ujis w2 [ fail ] Test ended at 2011-01-26 05:31:25 Server log is: 110126 7:31:24 [Note] Plugin 'FEDERATED' is disabled. 110126 5:31:24 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! 110126 5:31:24 InnoDB: The InnoDB memory heap is disabled 110126 5:31:24 InnoDB: Mutexes and rw_locks use Windows interlocked functions 110126 5:31:24 InnoDB: Compressed tables use zlib 1.2.3 110126 5:31:24 InnoDB: Initializing buffer pool, size = 8.0M 110126 5:31:24 InnoDB: Completed initialization of buffer pool 110126 5:31:24 InnoDB: highest supported file format is Barracuda. 110126 5:31:24 InnoDB: Assertion failure in thread 6416 in file ..\..\..\mysql-5.6.2-m5\storage\innobase\buf\buf0buf.c line 2740 InnoDB: Failing assertion: block->page.offset == page_get_page_no(page_align(ptr)) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 110126 7:31:24 - 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=1048576 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60653 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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... 000000013F6DD4A8 mysqld.exe!buf_block_align_instance()[buf0buf.c:2740] 000000013F6DD581 mysqld.exe!buf_block_align()[buf0buf.c:2769] 000000013F792207 mysqld.exe!mtr_memo_contains_page()[mtr0mtr.c:394] 000000013F792044 mysqld.exe!mtr_read_ulint()[mtr0mtr.c:370] 000000013F7C44D4 mysqld.exe!trx_undo_mem_create_at_db_start()[trx0undo.c:1293] 000000013F7C42B9 mysqld.exe!trx_undo_lists_init()[trx0undo.c:1418] 000000013F6C8911 mysqld.exe!trx_rseg_mem_create()[trx0rseg.c:202] 000000013F6C8DC4 mysqld.exe!trx_rseg_create_instance()[trx0rseg.c:276] 000000013F6C8C09 mysqld.exe!trx_rseg_list_and_array_init()[trx0rseg.c:341] 000000013F68B0EC mysqld.exe!trx_sys_init_at_db_start()[trx0sys.c:974] 000000013F669A95 mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1719] 000000013F625DA9 mysqld.exe!innobase_init()[ha_innodb.cc:2673] 000000013F1D9A16 mysqld.exe!ha_initialize_handlerton()[handler.cc:475] 000000013F1CFA69 mysqld.exe!plugin_initialize()[sql_plugin.cc:1063] 000000013F1CF792 mysqld.exe!plugin_init()[sql_plugin.cc:1344] 000000013F1B8772 mysqld.exe!init_server_components()[mysqld.cc:4114] 000000013F1B5961 mysqld.exe!win_main()[mysqld.cc:4675] 000000013F1B95F4 mysqld.exe!mysql_service()[mysqld.cc:4884] 000000013F1B9A52 mysqld.exe!mysqld_main()[mysqld.cc:5070] 000000013F1B1034 mysqld.exe!main()[main.cc:25] 000000013F96AEA7 mysqld.exe!__tmainCRTStartup()[crt0.c:266] 000000013F96ADAE mysqld.exe!mainCRTStartup()[crt0.c:182] 000000007751BE3D kernel32.dll!BaseThreadInitThunk() 0000000077656A51 ntdll.dll!RtlUserThreadStart() 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. Writing a core file Minidump written to Q:\pb2\test\sb_1-2883757-1295998435.4\mysql-5.6.2-m5-winx64\mysql-test\var-jp\2\mysqld.1\data\mysqld.dmp How to repeat: http://pb2.norway.sun.com/?template=mysql_show_test_failure&search=yes&push_id=1958184&tes...