加入收藏 | 设为首页 | 会员中心 | 我要投稿 济南站长网 (https://www.0531zz.com/)- 科技、建站、经验、云计算、5G、大数据,站长网!
当前位置: 首页 > 站长学院 > MySql教程 > 正文

mysqldump死住问题(实际是导致mysqld crash)

发布时间:2016-09-05 11:14:18 所属栏目:MySql教程 来源:站长网
导读:在MySQL 5.0.16上,用mysqldump导出数据,mysqldump半天没反应。 操作系统是RHEL4.0。 看日志 *** glibc detected *** free(): invalid pointer: 0xb17d60b0 **
在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 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=8388600

read_buffer_size=131072

max_used_connections=2

max_connections=100

threads_connected=2

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K

bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

thd=0x9d69ba0

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=0xb17d5a6c, backtrace may not be correct.

Stack range sanity check OK, backtrace follows:

0x815f652

0x9ed7c8

(nil)

0x81d40a

0x823b3f

0x823eba

0x819eb85

0x819f5bf

0x819f7f9

0x82314e9

0x8178872

0x817db98

0x817e59c

0x817f99c

0x9e7341

0x8896fe

(编辑:济南站长网)

【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!

    热点阅读