Continuous mysql signal 11 (or worse)

All of a sudden, I cant get mysql to start. Its looping with signal 11, filling up the logs with the output below. I'm running Redhat 9 & haven't changed the config in months.

Even worse I that I've found files like C:\windows\system32\shell64.dll under /var with modification dates in the last month.

Is this a mysql problem or have I been hacked?

–--------

Number of processes running now: 0

050614 01:25:27 mysqld restarted

050614 1:25:28 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…

050614 1:25:28 InnoDB: Starting log scan based on checkpoint at

InnoDB: log sequence number 0 43634.

InnoDB: Doing recovery: scanned up to log sequence number 0 43634

050614 1:25:28 InnoDB: Flushing modified pages from the buffer pool…

050614 1:25:28 InnoDB: Started; log sequence number 0 43634

050614 1:25:28 Found an entry in the 'db' table with empty database name; Skipped

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.

keybuffersize=5242880

readbuffersize=131072

maxusedconnections=0

max_connections=100

threads_connected=0

It is possible that mysqld could use up to

keybuffersize + (readbuffersize + sortbuffersize)*max_connections = 427519 K

bytes of memory

Hope that's ok; if not, decrease some variables in the equation.