mysqld got signal 10;
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=76
max_connections=75
threads_connected=27
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 171391 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

060729 15:29:51  mysqld restarted
060729 15:29:51  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...
060729 15:29:51  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 89 3069250346.
InnoDB: Doing recovery: scanned up to log sequence number 89 3069250346
060729 15:29:51  InnoDB: Started; log sequence number 89 3069250346
060729 15:29:51 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.0.22'  socket: '/tmp/mysql.sock'  port: 3306  FreeBSD port: mysql-server-5.0.22