Hello.
If you are able to use a DBUG package on a production server - do it. You may limit debugging to the list of named functions with 'f' flag. See: http://dev.mysql.com/doc/mysql/en/the-dbug-package.html Send an output of 'SHOW VARIABLES', 'SHOW STATUS', ulimits for mysql user. "Andrew Braithwaite" <[EMAIL PROTECTED]> wrote: > Hi, > > I have loaded and ran mysql-debug-4.1.10a and am getting the same > problem. > > There are no errors produced in the error log and mysqld is not crashing > so there is no stack trace to resolve. > > Any ideas? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
