Mysqldump (actually caused by mysqldcrash) _ MySQL

Mysqldump (actually caused by mysqldcrash)

On MySQL 5.0.16, mysqldump is used to export data. mysqldump does not respond for half a day.

The operating system is RHEL4.0.

View Logs

* ** Glibc detected ** free (): invalid pointer: 0xb17d60b0 ***

Mysqld got signal 6;

This cocould be because you hit a bug. It is also possible that this binary

Or one of the libraries it was linked against is too UPT, 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 cocould use up

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)