060607 19:55:43  mysqld restarted
060607 19:55:44  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060607 19:55:44  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 20 36601436.
InnoDB: Doing recovery: scanned up to log sequence number 20 36601474
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 27180154, file name prodipdb01-bin.000435
InnoDB: Last MySQL binlog file position 0 79, file name ./prodipdb02-bin.000793
060607 19:55:44  InnoDB: Flushing modified pages from the buffer pool...
060607 19:55:44  InnoDB: Started; log sequence number 20 36601474
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=67108864
read_buffer_size=4190208
max_used_connections=0
max_connections=1000
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2011224 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xa8911b0
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=0xbfff9f18, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a4a04
0x82b9cbc
0x8172fe0
0x819e046
0x8125425
0x8125836
0x815fbee
0x80a51c7
0x82c5b80
0x8048121
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 (nil)  is invalid pointer
thd->thread_id=0
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.