Home  >  Article  >  Database  >  mysqldump死住(实际是导致mysqld crash)_MySQL

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

WBOY
WBOYOriginal
2016-06-01 13:54:021455browse

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)

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn