first was an error message in log file ...
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died
Attemping backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong
stack range sanity check, ok, backtrace follows
0x2ab204d7
0x812ca95
0x812d595
0x81330a2
0x8133145
0x8133145
0x8133145
0x8133d50
0x8132de3
0x8106d55
0x80ec485
0x80ebd8d
0x80c5163
0x80c811a
0x80c321a
0x80c2797
stack trace successful
as in documentation I've done
# resolve_stack_dump -s mysql.sym -n last.stack
and this is an answer .. does anybody have an idea what can I do with this
?
db:/raid # resolve_stack_dump -s mysql.sym -n last.stack
0x2ab204d7 _end + 580057983
0x812ca95 _nisam_key_cmp + 1337
0x812d595 _nisam_bin_search + 137
0x81330a2 w_search + 190
0x8133145 w_search + 353
0x8133145 w_search + 353
0x8133145 w_search + 353
0x8133d50 _nisam_ck_write + 60
0x8132de3 nisam_write + 243
0x8106d55 write_row__7ha_isamPc + 101
0x80ec485 write_record__FP8st_tableP12st_copy_info + 501
0x80ebd8d
mysql_insert__FP3THDP13st_table_listRt4List1Z4ItemRt4List1Zt4List1Z4Item15enum_duplicates13thr_lock_type
+ 1077
0x80c5163 mysql_execute_command__Fv + 5403
0x80c811a mysql_parse__FP3THDPcUi + 206
0x80c321a do_command__FP3THD + 1278
0x80c2797 handle_one_connection__FPv + 679
Jan Matis
-
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
