Voytek: This is in regards to your post regarding the problems you were having with MySQL getting signal 11 with the stack trace, and some follow up messages. First some background. Signal 11 (SIGSEGV) happens when a program tries to follow an invalid memory reference. While this is possible to happen on bad hardware or buggy OS, most of the time, this is caused by a bug in the logic of the application. In this case, it is very useful to take a look at the properly generated core file - memory image of the application at the time of the crash. We have found that with LinuxThreads coredumps are very flaky and added some internal backtracing code to MySQL which intercepts SIGSEGV, SIGBUS ( bus error) and SIGILL ( illegal instruction), and does its own numeric backtrace which can be resolved later using resolve_stack_dump utility. The instructions for doing the resolve are found at http://www.mysql.com/doc/U/s/Using_stack_trace.html . While even the resolved output is not very meaningful and is even rather confusing to the user, it quite meaningful to us, as it tells us where in the code the crash happened, and gives us a lead on tracking down the bug. So whenever you see the stack trace in your error log, you should *always* resolve it and report it. Your server will in most cases happily restart after such a crash, but you may have some corrupted tables to repair. So both you and us want to get all those bugs out. Our stack tracer code additionally will try to get the query and the thread id that crashed when possible. If it ever crashes on your system with a query, you should copy the tables to a test server, re-run the query to verify the crash, and then send the tables along with the query to us. The tables should be FTP'ed to ftp://support.mysql.com/pub/mysql/secret/ and the message should be sent, along with the query and mysqlbug output to [EMAIL PROTECTED] Voytek - I will now try to reproduce the crash you have reported on my system. In the mean time, can you send us the resolve of the stack trace. Others that are withholding their stack dumps/resolves from us - send them now ( resolved with resolve_stack_dump) or you will have to live with those bugs until 3.23.37 at least. -- MySQL Development Team __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA <___/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
