On Monday 29 April 2002 07:36 am, Wouter de Jong wrote: > > In addition, here the resolved stack-trace: > > > > 0x806cb54 handle_segfault__Fi + 428 > > 0x8116c2a pthread_sighandler + 158 > > 0x80e715e mi_lock_database + 14 > > 0x80b5de8 external_lock__9ha_myisamP3THDi + 28 > > 0x8069d75 lock_external__FPP8st_tableUi + 121 > > 0x8069bea mysql_lock_tables__FP3THDPP8st_tableUi + 362 > > 0x8084e34 lock_tables__FP3THDP13st_table_list + 108 > > 0x808725d open_and_lock_tables__FP3THDP13st_table_list + 41 > > 0x80736ac mysql_execute_command__Fv + 696 > > 0x8077808 mysql_parse__FP3THDPcUi + 216 > > 0x80728f4 do_command__FP3THD + 1460 > > 0x8071ca7 handle_one_connection__FPv + 651 > > Forgot to mention that this stack-trace happened while running 3.23.47 > ... the resolved stack-trace is also on the 3.23.47 binary
Wouter: It appears that you are experiencing some memory corruption. The crash seems to be happening in a very stable area of code. It is, of course, possible that we have a very strange bug, but my intuition tells me this is a kernel problem in the VM code - we are getting a corrupted page. Can you try a different kernel? I would recommend that you try stock SuSE 7.3 if that is an option for you. -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/?ref=mspa __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / 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
