Damn!
It took longer, but crashed again. The stack trace has been the same as the
last three crashes:
# resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack
0x40097532 __evoke_link_warning_llseek + 937652786
0x80b3360
mysql_update__FP3THDP13st_table_listRt4List1Z4ItemT2P4ItemUl15enum_duplicate
s13thr_lock_type + 2480
0x80b3595
mysql_update__FP3THDP13st_table_listRt4List1Z4ItemT2P4ItemUl15enum_duplicate
s13thr_lock_type + 3045
0x80bf1a4 pack_fields__FiRt4List1Z12create_field + 320
0x80bf4d9 make_empty_rec__Fi7db_typeUiRt4List1Z12create_fieldUiUi + 309
mysql_update() seems to be a problem area (or is getting bad data it is not
checking). Is there a way to interpret the above into lines of code? What is
the '+ 2480' above in reference to?
I'm going nuts.
If anyone else has a strace in there error log when mysql 3.23.333 crashes,
can you send me the part that looks like:
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
0x40097532
0x80b3360
0x80b3595
0x80bf1a4
0x80bf4d9
stack trace successful, now will try to get some
variables. Some pointers may be invalid and cause dump abort
thd->query at (nil) =
Thanks,
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
---------------------------------------------------------------------
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
