I knew that 5.1.x should be cooked by cmake.exe, so I made the source code of 5.1.41 using cmake.exe, and now the situation is that source can be built successful in VS2008, but when I run(or debug) it, there will be one notification about breakpoint. When I run the mysqld.exe in commandline, there will more clear infomation, but I don't know how to fix it. And the structure of soucre has changed from 5.1.x, shall we have a nice experience to share about how to build it in Windows and how to run it without err? What congfig need I do? Welcome your communication!
this is my crash information in console:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd /d E:\TestRoot\mysql-5.1.41\sql\Debug
E:\TestRoot\mysql-5.1.41\sql\Debug>mysqld.exe
100415 16:47:15 [ERROR] Can't find messagefile 'E:\TestRoot\mysql-5.1.41 ql\shar
e\english\errmsg.sys'
100415 16:47:15 [Warning] Can't create test file E:\TestRoot\mysql-5.1.41 ql\dat
a\gtest.lower-test
100415 16:47:15 [Warning] Can't create test file E:\TestRoot\mysql-5.1.41 ql\dat
a\gtest.lower-test
Assertion failed: 0, file .\mysqld.cc, line 4247
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.
100415 16:47:15 - 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=0
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32632 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 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...
013C4D73 mysqld.exe!my_sigabrt_handler()[mysqld.cc:2048]
0138932B mysqld.exe!raise()[winsig.c:590]
013918A5 mysqld.exe!abort()[abort.c:71]
0181ED96 mysqld.exe!_wassert()[assert.c:163]
013C88A9 mysqld.exe!test_lc_time_sz()[mysqld.cc:4247]
013C594C mysqld.exe!win_main()[mysqld.cc:4361]
013C89C8 mysqld.exe!mysql_service()[mysqld.cc:4577]
013C8D3A mysqld.exe!main()[mysqld.cc:4763]
01381137 mysqld.exe!__tmainCRTStartup()[crt0.c:266]
0138100F mysqld.exe!mainCRTStartup()[crt0.c:182]
75033677 kernel32.dll!BaseThreadInitThunk()
77229D72 ntdll.dll!RtlInitializeExceptionChain()
77229D45 ntdll.dll!RtlInitializeExceptionChain()
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.
Thank all firstly! I need HELP!