Dyntex.net Support Centre: MySQL Reference Manual p.759

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Appendix E: Porting to Other Systems 759 however quite slow, so if you get performance problems you should start mysqld with the --skip-safemalloc option. This will disable the memory overrun checks for each call to malloc and free. If mysqld stops crashing when you compile it with --with-debug, you have probably found a compiler bug or a timing bug within MySQL. In this case you can try to add -g to the CFLAGS and CXXFLAGS variables above and not use --with-debug. If mysqld now dies, you can at least attach to it with gdb or use gdb on the core le to nd out what happened. When you congure MySQL for debugging you automatically enable a lot of extra safety check functions that monitor the health of mysqld. If they nd something \unexpected," an entry will be written to stderr, which safe_mysqld directs to the error log! This also means that if you are having some unexpected problems with MySQL and are using a source distribution, the rst thing you should do is to congure MySQL for debugging! (The second thing, of course, is to send mail to mysql@lists.mysql.com and ask for help. Please use the mysqlbug script for all bug reports or questions regarding the MySQL version you are using! In the Windows MySQL distribution, mysqld.exe is by default compiled with support for trace les. E.1.2 Creating Trace Files If the mysqld server doesn't start or if you can cause the mysqld server to crash quickly, you can try to create a trace le to nd the problem. To do this you have to have a mysqld that is compiled for debugging. You can check this by executing mysqld -V. If the version number ends with -debug, it's compiled with support for trace les. Start the mysqld server with a trace log in `/tmp/mysqld.trace' (or `C:\mysqld.trace' on Windows): mysqld --debug On Windows you should also use the --standalone ag to not start mysqld as a service: In a DOS window do: mysqld --debug --standalone After this you can use the mysql.exe command-line tool in a second DOS window to reproduce the problem. You can take down the above mysqld server with mysqladmin shutdown. Note that the trace le will get very big! If you want to have a smaller trace le, you can use something like: mysqld --debug=d,info,error,query,general,where:O,/tmp/mysqld.trace which only prints information with the most interesting tags in `/tmp/mysqld.trace'. If you make a bug report about this, please only send the lines from the trace le to the appropriate mailing list where something seems to go wrong! If you can't lo- cate the wrong place, you can ftp the trace le, together with a full bug report, to ftp://support.mysql.com/pub/mysql/secret/ so that a MySQL developer can take a look a this.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide