H:\mysql\5.5\5.5.3\mysql-5.5.3-m3-winx64\bin>mysqld-debug --no-defaults --console --skip-gr --skip-na 100415 12:29:03 [Note] Buffered information: Performance schema disabled (reason: start parameters). 100415 12:29:03 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use Windows interlocked functions InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 100415 12:29:04 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100415 12:29:04 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... 100415 12:29:04 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 100415 12:29:05 InnoDB Plugin 1.0.6 started; log sequence number 0 100415 12:29:05 [Note] mysqld-debug: ready for connections. Version: '5.5.3-m3-community-debug' socket: '' port: 3306 MySQL Community Server - Debug (GPL) 100415 12:29:27 - 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=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338278 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0xc93de00 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... 0000000140598080 gmtime_r() 000000014014DA3F ?gmt_sec_to_TIME@Time_zone_utc@@UEBAXPEAUst_mysql_time@@J@Z() 00000001403082A4 ?store_now_in_TIME@Item_func_curdate_utc@@UEAAXPEAUst_mysql_time@@@Z() 00000001403080BC ?fix_length_and_dec@Item_func_curdate@@UEAAXXZ() 0000000140103DAE ?fix_fields@Item_func@@UEAA_NPEAVTHD@@PEAPEAVItem@@@Z() 00000001400B5FC1 ?setup_fields@@YA_NPEAVTHD@@PEAPEAVItem@@AEAV?$List@VItem@@@@W4enum_mark_columns@@PEAV3@_N@Z() 0000000140250915 ?prepare@JOIN@@QEAAHPEAPEAPEAVItem@@PEAUTABLE_LIST@@IPEAV2@IPEAUst_order@@323PEAVst_select_lex@@PEAVst_select_lex_unit@@@Z() 000000014025860C ?mysql_select@@YA_NPEAVTHD@@PEAPEAPEAVItem@@PEAUTABLE_LIST@@IAEAV?$List@VItem@@@@PEAV2@IPEAUst_order@@545_KPEAVselect_result@@PEAVst_select_lex_unit@@PEAVst_select_lex@@@Z() 0000000140250013 ?handle_select@@YA_NPEAVTHD@@PEAULEX@@PEAVselect_result@@K@Z() 00000001401A3CDE ?mysql_execute_command@@YAHPEAVTHD@@@Z() 000000014019B7DB ?mysql_execute_command@@YAHPEAVTHD@@@Z() 00000001401A6375 ?mysql_parse@@YAXPEAVTHD@@PEBDIPEAPEBD@Z() 000000014019909A ?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI@Z() 0000000140198686 ?do_command@@YA_NPEAVTHD@@@Z() 0000000140082CCE ?do_handle_one_connection@@YAXPEAVTHD@@@Z() 0000000140082AC7 handle_one_connection() 000000014058F2DB pthread_create() 00000001406A4DF5 my_strnncoll_gbk() 00000001406A4DC8 my_strnncoll_gbk() 0000000077D6B6CA BaseThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 000000000C979250=select utc_date() thd->thread_id=1 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.5\5.5.3\mysql-5.5.3-m3-win32\bin>mysqld-debug --no-defaults --console --skip-gr --skip-na 100415 12:33:07 [Note] Buffered information: Performance schema disabled (reason: start parameters). 100415 12:33:07 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use Windows interlocked functions InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 100415 12:33:07 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100415 12:33:07 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... 100415 12:33:08 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 100415 12:33:08 InnoDB Plugin 1.0.6 started; log sequence number 0 100415 12:33:08 [Note] mysqld-debug: ready for connections. Version: '5.5.3-m3-community-debug' socket: '' port: 3306 MySQL Community Server - Debug (GPL) 100415 12:33:12 - 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=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337835 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x605f380 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... 0088DBDB mysqld-debug.exe!gmtime_r() 00517412 mysqld-debug.exe!?gmt_sec_to_TIME@Time_zone_utc@@UBEXPAUst_mysql_time@@J@Z() 006836F5 mysqld-debug.exe!?store_now_in_TIME@Item_func_curdate_utc@@UAEXPAUst_mysql_time@@@Z() 00683562 mysqld-debug.exe!?fix_length_and_dec@Item_func_curdate@@UAEXXZ() 004D921A mysqld-debug.exe!?fix_fields@Item_func@@UAE_NPAVTHD@@PAPAVItem@@@Z() 0049B169 mysqld-debug.exe!?setup_fields@@YA_NPAVTHD@@PAPAVItem@@AAV?$List@VItem@@@@W4enum_mark_columns@@PAV3@_N@Z() 005EC0CC mysqld-debug.exe!?prepare@JOIN@@QAEHPAPAPAVItem@@PAUTABLE_LIST@@IPAV2@IPAUst_order@@323PAVst_select_lex@@PAVst_select_lex_unit@@@Z() 005F21A8 mysqld-debug.exe!?mysql_select@@YA_NPAVTHD@@PAPAPAVItem@@PAUTABLE_LIST@@IAAV?$List@VItem@@@@PAV2@IPAUst_order@@545_KPAVselect_result@@PAVst_select_lex_unit@@PAVst_select_lex@@@Z() 005EBA81 mysqld-debug.exe!?handle_select@@YA_NPAVTHD@@PAULEX@@PAVselect_result@@K@Z() 0055E75F mysqld-debug.exe!?mysql_execute_command@@YAHPAVTHD@@@Z() 00557CFC mysqld-debug.exe!?mysql_execute_command@@YAHPAVTHD@@@Z() 00560648 mysqld-debug.exe!?mysql_parse@@YAXPAVTHD@@PBDIPAPBD@Z() 00555D40 mysqld-debug.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z() 005555B9 mysqld-debug.exe!?do_command@@YA_NPAVTHD@@@Z() 00470802 mysqld-debug.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z() 004705FC mysqld-debug.exe!handle_one_connection() 00886228 mysqld-debug.exe!pthread_create() 00961743 mysqld-debug.exe!my_strnncoll_gbk() 009616E4 mysqld-debug.exe!my_strnncoll_gbk() 7D4E0017 kernel32.dll!FlsSetValue() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 06095C00=select utc_date() thd->thread_id=1 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.5\5.5.2\mysql-5.5.2-m2-win32\bin>mysqld-debug --no-defaults --console --skip-gr --skip-na 100415 12:36:45 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use Windows interlocked functions InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 100415 12:36:46 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100415 12:36:46 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... 100415 12:36:46 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 100415 12:36:47 InnoDB Plugin 1.0.6 started; log sequence number 0 100415 12:36:47 [Note] mysqld-debug: ready for connections. Version: '5.5.2-m2-community-debug' socket: '' port: 3306 MySQL Community Server - Debug (GPL) 100415 12:36:54 - 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 = 337730 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x4fe8550 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... 008BF1DB mysqld-debug.exe!gmtime_r()[my_pthread.c:166] 00551D72 mysqld-debug.exe!Time_zone_utc::gmt_sec_to_TIME()[tztime.cc:1157] 00698A15 mysqld-debug.exe!Item_func_curdate_utc::store_now_in_TIME()[item_timefunc.cc:1632] 0069887C mysqld-debug.exe!Item_func_curdate::fix_length_and_dec()[item_timefunc.cc:1592] 005036B7 mysqld-debug.exe!Item_func::fix_fields()[item_func.cc:198] 00526F19 mysqld-debug.exe!setup_fields()[sql_base.cc:7494] 0060B6E9 mysqld-debug.exe!JOIN::prepare()[sql_select.cc:506] 00611748 mysqld-debug.exe!mysql_select()[sql_select.cc:2462] 0060B0F1 mysqld-debug.exe!handle_select()[sql_select.cc:272] 00598E1F mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5194] 0059130D mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2290] 0059AD5C mysqld-debug.exe!mysql_parse()[sql_parse.cc:6211] 0058F41C mysqld-debug.exe!dispatch_command()[sql_parse.cc:1242] 0058EA9C mysqld-debug.exe!do_command()[sql_parse.cc:875] 0049F88A mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1154] 008B9428 mysqld-debug.exe!pthread_start()[my_winthread.c:61] 009709A1 mysqld-debug.exe!_callthreadstartex()[threadex.c:348] 00970942 mysqld-debug.exe!_threadstartex()[threadex.c:331] 7D4E0017 kernel32.dll!FlsSetValue() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 05E37D20=select utc_date() thd->thread_id=1 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.45\mysql-advanced-gpl-5.1.45-winx64\bin>mysqld-debug --no-defaults --console --skip-gr --skip-na 100415 12:38:20 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 100415 12:38:20 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100415 12:38:21 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... 100415 12:38:21 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 100415 12:38:21 InnoDB: Started; log sequence number 0 0 100415 12:38:21 [Note] mysqld-debug: ready for connections. Version: '5.1.45-enterprise-gpl-advanced-debug' socket: '' port: 3306 MySQL Enterprise Server - Advanced Edition Debug (GPL) 100415 12:38: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 = 338112 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x4c4f198 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... 000000014060E0D7 mysqld-debug.exe!gmtime_r()[my_pthread.c:166] 00000001401B18BF mysqld-debug.exe!Time_zone_utc::gmt_sec_to_TIME()[tztime.cc:1158] 000000014035CF4B mysqld-debug.exe!Item_func_curdate_utc::store_now_in_TIME()[item_timefunc.cc:1584] 000000014035CD3B mysqld-debug.exe!Item_func_curdate::fix_length_and_dec()[item_timefunc.cc:1542] 0000000140146FEB mysqld-debug.exe!Item_func::fix_fields()[item_func.cc:199] 000000014017668F mysqld-debug.exe!setup_fields()[sql_base.cc:7499] 00000001402A79C0 mysqld-debug.exe!JOIN::prepare()[sql_select.cc:521] 00000001402B0537 mysqld-debug.exe!mysql_select()[sql_select.cc:2464] 00000001402A6FD8 mysqld-debug.exe!handle_select()[sql_select.cc:269] 00000001402109CA mysqld-debug.exe!execute_sqlcom_select()[sql_parse.cc:5052] 0000000140206C55 mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:2248] 0000000140213735 mysqld-debug.exe!mysql_parse()[sql_parse.cc:5975] 000000014020423B mysqld-debug.exe!dispatch_command()[sql_parse.cc:1235] 00000001402034EA mysqld-debug.exe!do_command()[sql_parse.cc:874] 00000001400C7235 mysqld-debug.exe!handle_one_connection()[sql_connect.cc:1127] 0000000140604ED5 mysqld-debug.exe!pthread_start()[my_winthread.c:85] 00000001405DB145 mysqld-debug.exe!_callthreadstart()[thread.c:295] 00000001405DB117 mysqld-debug.exe!_threadstart()[thread.c:277] 0000000077D6B6CA kernel32.dll!BaseThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0000000004C44C88=select utc_date() thd->thread_id=1 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.45\mysql-advanced-gpl-5.1.45-winx64\bin>