mysqldump死住（实际是导致mysqldcrash）_MySQL
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了mysqldump死住（实际是导致mysqldcrash）_MySQL，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含1358字，纯文字阅读大概需要2分钟。
内容图文
mysqldump
在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)
内容总结
以上是互联网集市为您收集整理的mysqldump死住（实际是导致mysqldcrash）_MySQL全部内容，希望文章能够帮你解决mysqldump死住（实际是导致mysqldcrash）_MySQL所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。