030924 08:05:08  mysqld started
030924  8:05:09  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 13 1700811975
InnoDB: Doing recovery: scanned up to log sequence number 13 1700811975
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=4190208
sort_buffer_size=1919252082
max_used_connections=0
max_connections=650
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 785799 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
thd=0x8448fe8
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...

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 785799 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
thd=0x8448fe8
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=0xbfffe4b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80720ba
0x828fd7e
0x81d1c5e
0x81c7838
0x81c26fc
0x81d7e6a
0x8100eb2
0x80cd0a4
0x80c7d30
0x8072f47
0x82a23b2
0x8048101
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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 (nil)  is invalid pointer
thd->thread_id=842100835
 
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 842100835 did to cause the crash.  In some cases of really
bad corruption, the values shown above may be invalid.
 
The manual page at http://www.mysql.com/doc/C/r/Crashing.html containsjinformation thad`should help you find out what is causing the crash.
030924 08:05:09  mysqld ended