If the mysqld server doesn't start or if you can cause it to crash quickly, you can try to create a trace file to find the problem.
To do this, you must have a mysqld that has
been compiled with debugging support. You can check this by
mysqld -V. If the version number
-debug, it is compiled with
support for trace files. (On Windows, the debugging server is
named mysqld-debug rather than
mysqld as of MySQL 4.1.)
Start the mysqld server with a trace log in
/tmp/mysqld.trace on Unix or
C:\mysqld.trace on Windows:
mysqld-debug --debug --standalone
The trace file can become very large! To generate a smaller trace file, you can use debugging options something like this:
This only prints information with the most interesting tags to the trace file.
If you make a bug report about this, please only send the lines from the trace file to the appropriate mailing list where something seems to go wrong! If you can't locate the wrong place, you can open a bug report and upload the trace file to the report, so that a MySQL developer can take a look at it. For instructions, see Section 1.8, “How to Report Bugs or Problems”.
The trace file is made with the DBUG package by Fred Fish. See Section 18.4.3, “The DBUG Package”.