Another signal 11 dump ... cutting down sort_buffer to 4194296 Bytes
seems not to be the solution for the signal 11 at 0 o'clock ... stated
some weeks ago!
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
0x4001d65d
0x80d7664
0x80b7d2d
0x80dab94
0x80dab19
0x80c3629
0x80c67e2
0x80c27f3
0x80c1b57
stack trace successful, now will try to get some
variables. Some pointers may be invalid and cause dump abort
thd->query at 0x4a810060 is invalid pointer
thd->thread_id = 65207
successfully dumped variables, if you ran with --log
take a look at the details of what thread 65207 did to cause the crash.
In some cases of really bad corruption, this value can be invalid
Please use the information above to create a repeatable
test case for the crash, and send it to [EMAIL PROTECTED]
Number of processes running now: 0
010522 23:55:18 mysqld restarted
---------------------------------------------------------------------
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
