Stephen, I resolved the stack dump based on the 3.23.43 symbols file. I do not understand what mysqld is trying to do here. Are you sure the stack dump is from 3.23.43?
0x807b90f init_signals__Fv + 71 0x8253c7a __tfx + 26 0x80cf21a index_prev__11ha_innobasePc + 74 0x8078693 mysql_lock_remove__FP3THDP13st_mysql_lockP8st_table + 99 0x807853d mysql_lock_tables__FP3THDPP8st_tableUi + 557 0x80b202b acl_init__Fb + 795 0x807c656 main + 2678 0x82639fb __printf_fp + 5027 0x8048111 _start + 33 3.23.44 has a new my.cnf parameter. You could try set-variable = innodb_force_recovery=2 Does it now start to run? You can then try to dump your tables. See the manual at http://www.innodb.com/ibman.html section 6.1 about forcing recovery. Regards, Heikki Innobase Oy --------------------------------------------------------------------- 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
