/usr/libexec/mysqld: ready for connections.
Version: '4.1.22-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
mysqld got signal 11;
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=402653184
read_buffer_size=1044480
max_used_connections=78
max_connections=500
threads_connected=68
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1927212 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x94e14cf8
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=0x94ac06b4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8139eec
0x4f6e67
0x831b884
0x81c22a7
0x81c3150
0x81b5f53
0x814f934
0x8151b3c
0x815255a
0x8152db5
0x815375b
0x4f5371
0x3f5ffe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa3d1038 = SAVEPOINT interspire4a0e91f2aa63e
thd->thread_id=758
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
090516 19:14:11  mysqld restarted