lnxdb1:~# /usr/local/mysql/libexec/mysqld  --basedir=/usr/local/mysql --datadir=/usr/local/mysql/var --user=mysql --pid-file=/usr/local/mysql/var/mysql.pid --skip-locking --log=/usr/local/mysql/var/mysql.log
060221 15:29:47  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...
060221 15:29:47  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 59399548.
InnoDB: Doing recovery: scanned up to log sequence number 0 59399548
InnoDB: Last MySQL binlog file position 0 0, file name 
060221 15:29:47  InnoDB: Started; log sequence number 0 59399548
060221 15:29:47 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.18-debug-log'  socket: '/usr/local/mysql/tmp/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=8388600
read_buffer_size=131072
max_used_connections=10
max_connections=100
threads_connected=8
It is possible that mysqld could use up to 
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=0x8be64d0
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=0xb50f6b2c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8191e03
0xffffe420
0x8cf4520
0x81adcc9
0x8216750
0x8216c64
0x81b34bb
0x81b4960
0x81b4d6c
0xb7f6de70
0xb7e98c0e
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 0x8bf2180 = delete from server_messages   using server_messages     left join messages_and_servers       on server_messages.id = messages_and_servers.message   where server_messages.id = 4     and messages_and_servers.message is null
thd->thread_id=3
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.