首页 / 数据库 / MySQL / mysqldump死住问题(实际是导致mysqld crash)
mysqldump死住问题(实际是导致mysqld crash)2011-10-20在MySQL 5.0.16上,用mysqldump导出数据,mysqldump半天没反应。操作系统是RHEL4.0。看日志*** glibc detected *** free(): invalid pointer: 0xb17d60b0 ***mysqld got signal 6;This could be because you hit a bug. It is also possible that this binaryor 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 diagnosethe problem, but since we have already crashed, something is definitely wrongand this may fail.key_buffer_size=8388600read_buffer_size=131072max_used_connections=2max_connections=100threads_connected=2It is possible that mysqld could use up tokey_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 Kbytes of memoryHope that"s ok; if not, decrease some variables in the equation.thd=0x9d69ba0Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...Cannot determine thread, fp=0xb17d5a6c, backtrace may not be correct.Stack range sanity check OK, backtrace follows:0x815f6520x9ed7c8(nil)0x81d40a0x823b3f0x823eba0x819eb850x819f5bf0x819f7f90x82314e90x81788720x817db980x817e59c0x817f99c0x9e73410x8896fe