4.0.6 + FLUSH QUERY CACHE -> mysqld got signal 11

4.0.6 + FLUSH QUERY CACHE -> mysqld got signal 11

am 25.12.2002 00:05:26 von Andrew Sitnikov

Hello mysql,

Hello mysql,

shell#>resolve_stack_dump -s mysqld.sym -n mysqld.stack
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=402 653 184
read_buffer_size=2093056
sort_buffer_size=2097144
max_used_connections=2
max_connections=200
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1211614 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x88ec5d0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xb761f208, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8071b8a handle_segfault + 450
0x82929e8 pthread_sighandler + 184
0x80f1673 move_by_type__11Query_cachePPcPP17Query_cache_blockPUlP17Que ry_cache_block + 875
0x80f124c pack_cache__11Query_cache + 196
0x80ee5f2 pack__11Query_cacheUlUi + 70
0x8081c9b reload_acl_and_cache__FP3THDUlP13st_table_list + 215
0x807f993 mysql_execute_command__Fv + 13067
0x80807e6 mysql_parse__FP3THDPcUi + 214
0x807bafa dispatch_command__F19enum_server_commandP3THDPcUi + 1594
0x807b4b6 do_command__FP3THD + 310
0x807ab8e handle_one_connection + 698
0x829019c pthread_start_thread + 220
0x82c58aa thread_start + 4
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the
stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x88efd10 = FLUSH QUERY CACHE
thd->thread_id=1643


mysql> show variables like 'query_cache%';
+-------------------+----------+
| Variable_name | Value |
+-------------------+----------+
| query_cache_limit | 1048576 |
| query_cache_size | 67108864 |
| query_cache_type | ON |
+-------------------+----------+
3 rows in set (0.00 sec)

mysql> show variables like 'version';
+-------------------+-----------------------------+
| Variable_name | Value |
+-------------------+-----------------------------+
| version | 4.0.6-gamma-debug-debug-log |
+-------------------+-----------------------------+
1 rows in set (0.00 sec)


Best regards,
Andrew Sitnikov
e-mail : sitnikov@infonet.ee
GSM: (+372) 56491109

Best regards,
Andrew Sitnikov
e-mail : sitnikov@infonet.ee
GSM: (+372) 56491109


------------------------------------------------------------ ---------
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
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php