在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死住（实际是导致mysqld crash）的文章能够对您有所帮助，如果您觉得这篇网站维护教程有用的话，别忘了推荐给您的朋友哦！如果您有好的经验方法，不妨拿出来和大家一起分享：假如每个人都拿出一个经验，那么我们都将额外的获取一堆他人的经验。
请记住本站永久域名：（黑客防线网安服务器维护方案维护基地）Www.Rongsen.Com.Cn